Home/SEO/React JS SEO, Done by Engineers in Your Repo
React pages that buyers find in search
React JS SEO concerns what crawlers receive when they open the routes on your site: the content, titles and links. We read the code responsible for those pages and make the changes it needs. The work arrives as pull requests from our engineers in your repository.
What is React JS SEO?
For a crawler, opening a React route can mean fetching the code and then running it to read the page. Google separates that work into crawling, rendering and indexing, and uses evergreen Chromium to render JavaScript. React SEO and ReactJS SEO refer to making the site's pages readable through that process. The code decides what content appears, which title describes it and which links lead to the next route.
Server-side rendering and pre-rendering provide content to bots that cannot execute JavaScript, and Google recommends them for speed as well. The other details also sit in the code. Each route can set a title and description with JavaScript; links need <a> elements with an href; navigation between views uses the History API. Missing pages need meaningful response codes, since returning a normal response for an absent route can cause a soft 404.
A marketer can write SEO tickets for engineers to pick up between product tasks. A plugin or crawler can identify issues for someone to investigate. Our engineers work directly in your repo, making the changes the search findings call for. The same question applies to each route into the work: does the correction reach the code serving the site? With Tin, the people investigating the page also implement the fix.
- Check the rendered content. A crawler needs to read the text on the route it visits.
- Describe individual pages. Titles and descriptions belong to the route whose content they describe.
- Connect pages with links. An
hrefgives crawlers an address to follow to the next route.
SEO fixes stuck behind product work cost searches
Product features fill the engineering backlog, and the React marketing site's rendering and navigation fixes keep waiting for a sprint.
- Crawlers miss the content. A bot that cannot execute JavaScript receives the shell of a browser-rendered page.
- Sections lack a crawlable path. Navigation handled only through clicks can leave Google without links to follow.
- Absent routes return success. A missing page with a normal response can be treated as a soft 404.
An engineer can investigate each of these faults in the code that serves the public routes.
Our engineers change the code search engines read
We work on the parts of the React site that determine what a crawler receives, including the response when a page is absent.
Make content readable
We add server-side rendering or pre-rendering to public routes where it is needed, so their content is available to users and crawlers.
Set page descriptions
We put a title and meta description on each route in the code, matching the description to the content a buyer reaches.
Fix the navigation
We build links with <a href> and use History API routing, giving crawlers addresses to follow between the app's public pages.
Repair page signals
We change missing-page response codes and examine sitemap and canonical tags, so those signals agree with the pages the site serves.
Your team merges each change we make
The marketing-site repository is our starting point. We prepare code changes there for your team to inspect and fit into its releases.
First
Start with public pages
We connect the outward-facing site's repository and focus the initial work on the marketing pages buyers reach before using the product.
Then
Investigate the evidence
The audit reads up to 100 public pages without changing them, and our people review its findings to locate the code behind each issue.
Next
Send the proposed fix
Our engineers make the changes and open a pull request; your team reviews and merges it through the company's own repository.
After deployment
Return to Search Console
We inspect the changed pages and use the weekly conversation to choose what to continue, change or stop from the evidence.
Example: cutting homepage load to 0.7 seconds
We changed a recruiting-research firm's homepage so it loaded in 0.7 seconds, down from 2.5 seconds. That gives a concrete example of our engineering work on a public site. Google makes the broader point about JavaScript pages: server-side rendering or pre-rendering can make them faster for both the person visiting and the crawler reading them.
The people who plan search also write code
Rendering and routing problems lead back to the code. Our search work includes engineers who can read that code and make the correction themselves. You work with experienced founders and engineers, including AI engineers from MIT, who connect the planned buyer pages with the changes those pages need.
- Plan pages with their fixes. We consider what buyers search for alongside the engineering work their destination pages need.
- Implement the finding. The engineers responsible for the site changes also participate in planning the search work.
- Record the code changes. Your git history retains the pull requests as a record your engineers can inspect.
It fits teams whose site runs on React
Founders with React sites
We handle the marketing site's rendering and routing issues while technical founders concentrate their engineering attention on the product.
AI-enabled service companies
We work on the public pages when the engineers who built the site are busy developing the software behind the service.
Startups building their marketing
We support pre-seed to Series A B2B companies with clients, a React site and no experienced marketing lead to direct the work.
Talk to Tin
Let's discuss what crawlers can read on your public routes and which fixes belong first. Our engineers can take on the search work with no long-term commitment.
FAQ
Will Google index pages that React renders in the browser?
Google can render their JavaScript with Chromium, but rendering and indexing are separate stages. We check what the route supplies and then examine its index status. Google's recommendation for server-side rendering or pre-rendering also accounts for other bots that cannot execute JavaScript themselves.
Will your work slow down our product releases?
Our changes arrive as pull requests that your engineers can review and merge on their release schedule. We begin in the marketing-site repository, focused on public pages. That lets the team inspect the proposed fixes and decide when they belong in a deployment.
What do you need from us to start?
Access to the marketing-site repo and Search Console gives us the code and search evidence to begin. We also learn about the company through conversations. About two hours of the founder's week is our aim for those discussions and decisions, with the actual time depending on the work.
Can our engineers run Tin's open-source audit themselves?
Yes. It reads the public site and returns findings with their evidence, leaving the site unchanged. Your engineers can use it to begin their inspection. If we handle the work, our engineers follow the audit through to the rendering, title, link and routing changes it calls for.
Talk through your React site with our engineers
Meet the founders and engineers who would work on your site. We can discuss how its public routes render, what search engines can read today and which changes would make sense to take on first.