Technical SEO Services That Get Every Page Crawled and Indexed
FactoryJet fixes the infrastructure under your rankings: crawling, indexing, Core Web Vitals, JavaScript rendering, migrations, structured data and AI crawler access. Our developers ship the fixes on Shopify, WordPress, Webflow and Next.js, then prove each one in Search Console.
Need a one-time diagnosis instead? See our SEO audit service.
What Technical SEO Services Are, in Plain Terms
Technical SEO services make sure search engines and AI crawlers can find, fetch, render and index every page that should rank, quickly and without errors. It is the infrastructure layer of SEO. Content and links only count once this layer works. A technical SEO agency finds the problems, and the good ones fix them.
An ongoing technical SEO service covers six jobs:
- Crawl and index control: robots.txt, sitemaps, canonicals, status codes and internal links
- Rendering: content in the HTML, not waiting on JavaScript
- Core Web Vitals: LCP, INP and CLS on real visits
- Migrations: redirects and monitoring when URLs change
- Structured data: JSON-LD that matches the page
- AI crawler access and logs: which bots get in, and what they actually fetch
Google's "good" Core Web Vitals are LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, measured at the 75th percentile of real page loads. web.dev ↗ Google Search Central ↗
Google processes JavaScript pages in three phases: crawling, rendering and indexing. It still calls server-side or pre-rendering a great idea, because not all bots can run JavaScript. That includes many AI crawlers. Google Search Central ↗
Crawl budget is a real problem for large sites, not most sites. Google's guide targets sites with over a million unique pages, or over 10,000 pages that change daily. Smaller sites should fix indexing and duplicates first. Google crawling docs ↗
To appear as a link in Google AI Overviews or AI Mode, a page must be indexed and eligible for a snippet. Google says there are no extra technical requirements. Technical SEO is the entry ticket to AI search, not a separate trick. Google Search Central ↗
FactoryJet runs technical SEO as a development job, not a reporting job. We build ecommerce stores, websites and AI agents, so the people who find a rendering bug or a redirect chain can also ship the fix. Bhavesh, our founder, and the team stay on after each fix to catch regressions from your next release.
Technical SEO vs. On-Page SEO vs. an SEO Audit
| Service | What it fixes | Who usually does it | How long it runs |
|---|---|---|---|
| On-page SEO content and HTML | Titles, headings, copy, images and internal links on each page | SEO writers and editors | Ongoing, page by page |
| SEO audit Own page ↗ | Nothing directly. It diagnoses technical, content and authority issues and ranks them | An SEO analyst | One time, then you decide who fixes what |
| AI SEO Own page ↗ | Whether ChatGPT, Perplexity and AI Overviews cite you | SEO and content specialists | Ongoing, tracked per engine |
| Technical SEO This page | Crawling, indexing, rendering, speed, redirects, schema and crawler access | Engineers who can change templates, servers and builds | Ongoing, with a check on every release |
What each costs depends on site size and how much is broken. See the US SEO cost guide and the SEO audit cost guide for typical market ranges. You get a fixed written scope after a short call.
Indexability
A page is indexable when a search engine is allowed to crawl it, gets a 200 response, can see its main content in the rendered HTML, finds no noindex rule, and picks it as the canonical version rather than a duplicate. Fail any one of those five and the page cannot rank, however good it is. Google's own documentation warns that robots.txt is not a way to keep a page out of search, and that a noindex rule only works if the page is not blocked from crawling. robots.txt ↗ noindex ↗
Technical SEO Services We Deliver
Crawling & Indexing Control
robots.txt, XML sitemaps, canonical tags, noindex rules, status codes and internal links, set so Google spends its time on the pages that earn money and skips the ones that should never rank.
JavaScript & Next.js Rendering
We make React, Next.js, Vue and headless storefronts send their content, links and metadata in the first HTML response, so search engines and AI crawlers that do not run scripts still see the page.
Core Web Vitals
Template-by-template fixes for LCP, INP and CLS, measured on real-user data, not a one-off lab score. Images, fonts, third-party scripts and app bloat are where most of the time goes.
Open the page ↗Migrations & Replatforming
Domain moves, redesigns and platform changes such as Magento or WooCommerce to Shopify, with every old URL mapped and redirected in one hop, and Search Console watched daily after launch.
Open the page ↗Structured Data
JSON-LD generated from the same data the page shows: Product and Offer, Organization, BreadcrumbList, Article and FAQPage. Tested in the Rich Results Test before it ships, never hand-copied.
AI Crawler Access & Log Files
robots.txt rules that name each search and AI bot on purpose, plus server log analysis that shows which crawlers actually visit, what they fetch, and where crawling is wasted.
Open the page ↗What We Check and Fix, Item by Item
Five groups, 40 specific checks. If a technical SEO company cannot hand you a list this specific, and say who will ship each fix, you are buying a report rather than the work.
Crawling and indexing
Before anything ranks, it has to be fetched and kept. Most lost traffic starts here, quietly.
8 checks- Page indexing report read row by row, with a reason for every excluded URL that matters
- robots.txt checked for rules that block templates, CSS or JavaScript by accident
- noindex never behind a robots.txt block, since Google cannot see a noindex it is not allowed to crawl
- Canonical tags self-referencing by default, and deliberate where they point elsewhere
- XML sitemaps split by type, holding only live, indexable, canonical URLs
- Soft 404s turned into real 404 or 410 responses
- Orphan pages linked from somewhere a crawler can reach
- Crawlable links as real anchor tags with an href, not click handlers
Rendering and JavaScript
Google renders JavaScript later, in a queue. Many AI crawlers do not render it at all.
8 checks- Rendered HTML compared with the raw HTML on every key template
- Main copy, links and metadata present in the first server response
- Client-side routes returning real status codes, not a 200 for a missing page
- Robots meta tags set on the server, never changed later by JavaScript
- Lazy-loaded content that does not wait for a click or a scroll to exist
- Hydration errors that swap content after load, found and fixed
- Dynamic rendering replaced with server-side or static rendering, as Google now advises
- HTML weight kept well inside the first 2MB that Googlebot fetches
Speed and Core Web Vitals
Measured at the 75th percentile of real visits, on phones and desktops separately.
8 checks- LCP element identified per template, then preloaded or made text
- Hero images resized, compressed and served in modern formats
- Fonts subset and preloaded so text does not flash or shift
- Third-party and app scripts deferred, trimmed or removed
- Long JavaScript tasks split up so taps respond in under 200ms
- Space reserved for images, embeds and banners to keep CLS under 0.1
- Server response time and CDN caching checked on uncached pages
- Field data tracked in Search Console, not only lab scores
Structure, schema and international
Clear signals about what each page is, who it is for, and which version to show.
8 checks- One H1 and a clean H1, H2, H3 order on every template
- Faceted navigation limited to the filter pages that deserve to rank
- Pagination crawlable, with unique URLs for each page of results
- Product and Offer markup matching the visible price and stock
- Organization and BreadcrumbList on every page that needs them
- Markup only for visible content, per Google's structured data policy
- hreflang with return links and an x-default, for multi-country sites
- Mobile parity: same content, links and schema on phone and desktop
Migrations, logs and AI crawlers
The work that protects traffic you already have, and opens the door to AI answers.
8 checks- Every old URL saved from crawls, analytics and backlink data before a move
- 301 or 308 redirects in one hop, kept for at least a year
- Redirect chains collapsed, and internal links pointed at final URLs
- Server logs filtered to verified Googlebot using reverse DNS
- Crawl waste on parameters, redirects and errors measured in the logs
- OAI-SearchBot, Claude-SearchBot, PerplexityBot allowed by name if you want AI citations
- Training bots such as GPTBot and Google-Extended decided on purpose
- Release checks so the next deploy does not undo last month's fixes
Every rule above comes from primary documentation: Google on canonicals ↗, sitemaps ↗, status codes ↗, crawlable links ↗, Googlebot's 2MB fetch limit ↗, mobile-first indexing ↗, hreflang ↗ and structured data policy ↗. No secret ruleset, just careful engineering.
Send Us the Pages That Should Be Ranking
Tell us which pages matter most. We check how Google crawls, renders and indexes them, and reply with the three problems we would fix first and who ships each one.
Rendering Options for React and Next.js Sites, Compared
Where your HTML is produced decides what crawlers see. Google handles JavaScript, but later and at a cost. Many AI crawlers do not run it at all, so content that exists only after scripts load may never reach an AI answer.
| Approach | What a crawler gets first | SEO risk | Google's position |
|---|---|---|---|
| Client-side rendering plain React SPA | A near-empty HTML shell plus scripts | High. Content, links and metadata depend on rendering, and soft 404s are common | Works, but needs care. JS SEO basics ↗ |
| Dynamic rendering bots get a prerendered copy | Full HTML, served only to bots | Medium. Two versions to keep in sync | A workaround, not a long-term solution. Dynamic rendering ↗ |
| Server-side rendering Next.js, Nuxt, Remix | Full HTML on every request | Low, if metadata and status codes are set on the server | Recommended |
| Static or hybrid rendering what we usually build | Full HTML built ahead of time, refreshed on change | Lowest, and usually the fastest LCP | Recommended |
Technical SEO by Platform
Every platform breaks in its own familiar ways. Knowing where to look first cuts the time from finding an issue to shipping the fix. These are the problems we see most often on each one.
Shopify & Shopify Plus
Common technical issuesCollection-scoped product URLs that create duplicates, app scripts that drag LCP, thin filtered collection pages, and themes that leave Product markup incomplete.
PLT‑02BigCommerce
Common technical issuesFaceted search URLs, duplicate category paths, B2B price lists hidden from crawlers by design, and theme speed on large category pages.
PLT‑03WordPress & WooCommerce
Common technical issuesPlugin and page-builder bloat, tag and archive pages competing with real pages, attachment URLs, and overlapping SEO plugins writing conflicting tags.
PLT‑04Webflow
Common technical issuesCMS collection pages with thin templates, missing canonical rules on filtered lists, image weight from the designer, and 301 rules that need care during migrations.
PLT‑05Next.js & React
Common technical issuesPages rendered only in the browser, soft 404s on client routes, metadata set after load, and heavy client bundles that fail INP.
PLT‑06Headless commerce
Common technical issuesTwo systems generating URLs, canonicals and sitemaps out of sync with the commerce back end, and structured data that has to be rebuilt by hand.
How We Work
Baseline
Search Console, a full crawl, a rendering sample per template, field Core Web Vitals and, on large sites, server logs.
Prioritize
Issues ranked by the pages and revenue they affect, not by how many a tool flagged.
Fix
We ship the code, or write tickets and review your developers' changes. You approve every deploy.
Verify
URL Inspection, the Page indexing report and field data confirm each fix. Closed means Google sees it.
Guard
Each release checked for regressions, with crawl, index and speed numbers in a monthly report.
A Technical SEO Company Should Show Its Working
Four rules we hold ourselves to, on this page and in every client report.
Every rule links to the source
Each technical claim on this page links to Google, OpenAI, Anthropic or Perplexity documentation. When the docs change, we change the advice. Googlebot's HTML fetch limit, for example, is now documented as 2MB.
No crawl budget scare for small sites
Google says crawl budget matters for very large or very fast-changing sites. If yours is a 60-page service site, we will tell you so, and spend the time on indexing and speed instead.
We separate AI search bots from training bots
Blocking GPTBot does not remove you from ChatGPT search, and Google-Extended does not affect Google Search. Blanket AI blocks confuse the two, so every bot is decided by name.
Case studies are still being written
We would rather publish nothing than a before-and-after number we cannot prove. Ask for live references on a call.
Who Ranks for Technical SEO Services in the US Today
US agency sites on Google's first page for technical seo services and technical seo agency, from DataForSEO (desktop, English, US) on 26 September 2026. Tool sites, directories and non-US agencies are left out. Positions move every week, so treat this as a snapshot and read each page yourself.
| Agency | Google position, 26 Sep 2026 | What their page offers | Also worth knowing |
|---|---|---|---|
| Thrive Agency thriveagency.com · Arlington, TX | technical seo servicesnot top 10technical seo agency#3 | Audits, crawl error fixes, migrations, speed, structured data, HTTPS, sitemaps and penalty recovery, plus an FAQ that touches on AI Overviews. | A large full-service agency. Its page does not cover log files, JavaScript rendering or AI crawler rules. |
| Siege Media siegemedia.com · Austin, TX | technical seo services#5technical seo agency#4 | Ranks with a list of the best technical SEO agencies rather than a service page. Lists its own headquarters as Austin, San Francisco, New York and Chicago. | Useful for building a shortlist. A roundup, not a scope of work. |
| Saffron Edge saffronedge.com · Totowa, NJ | technical seo services#9technical seo agencynot top 10 | Audits, migrations, schema, speed, mobile, log file analysis, sitemaps, robots.txt and canonical fixes, in a five-step process. | Lists log file analysis and JavaScript rendering as services, without detail on method. |
| FactoryJet This page | Not in the top 10 for either search today. | Developers who ship the fixes, JavaScript rendering and log file work described in detail, AI crawler rules per bot, and a check on every release. | Far less domain authority than the agencies above. If the most familiar name matters most, hire the incumbent. |
Comparing more agencies? Our lists of the best SEO agencies in the USA and the best ecommerce SEO agencies review more firms.
Technical SEO, Answered Directly
30 questions US buyers ask Google, most taken word for word from its People Also Ask boxes, answered without hedging and linked to the source.
Q01What does technical SEO include?
Technical SEO covers everything that decides whether search engines can find, fetch, render and index your pages. That means robots.txt, XML sitemaps, status codes and redirects, canonical tags, internal links, JavaScript rendering, Core Web Vitals, mobile parity, structured data, hreflang for multi-country sites, and today, which AI crawlers you let in. Content and backlinks sit on top of it. If the technical layer fails, the rest is invisible.
Q02What are some examples of technical SEO?
Common examples: fixing a robots.txt rule that blocks product pages, collapsing a three-hop redirect chain into one 301, setting a canonical tag on filtered category URLs, making a React page send its main text in the first HTML response, cutting a slow hero image so the page passes LCP, adding Product markup that matches the visible price, and adding hreflang so the right country page shows up in each market.
Q03What is the difference between on-page SEO and technical SEO?
On-page SEO is about what a page says: the title, headings, copy, images and internal links that match a search. Technical SEO is about whether the page can be crawled, rendered and indexed at all, and how fast and stable it is. A great page with a noindex tag never ranks. A fast, indexable page with thin copy ranks poorly. You need both, and they are usually done by different people.
Q04What is the difference between SEO and technical SEO?
SEO is the whole job of earning search traffic: technical work, content, and authority from other sites. Technical SEO is one part of it, the infrastructure layer. It is closer to engineering than marketing, because most fixes happen in templates, server settings and build pipelines rather than in the words on the page. That is why technical SEO is often best done by a team that can also ship code.
Q05What are the four types of SEO?
The usual split is technical SEO (crawling, indexing, speed, rendering), on-page SEO (the content and HTML of each page), off-page SEO (links and mentions from other sites), and local SEO (map results and Google Business Profile). Many teams now add a fifth, AI search optimization, which is about being cited by ChatGPT, Perplexity and Google AI Overviews. It depends heavily on the technical layer. AI SEO services ↗
Q06Do you need coding for technical SEO?
To find problems, not much. Crawlers and Search Console show most issues. To fix them, often yes. Rendering problems, template-level canonical bugs, redirect rules, image pipelines and structured data generated from product data all live in code. This is the gap where many technical SEO engagements stall: the audit is written, then waits months for a developer. Our developers ship the fixes themselves.
Q07How to do technical SEO step by step?
Start with Search Console: the Page indexing report shows which URLs Google skipped and why. Then crawl the site with a tool like Screaming Frog to find broken links, redirect chains and missing canonicals. Check robots.txt and sitemaps. Test key templates with URL Inspection to see the rendered HTML. Measure Core Web Vitals from real-user data. Fix in order of pages that earn money, then re-check in Search Console. Google: Search Console Page indexing report ↗
Q08What does a technical SEO agency do?
A technical SEO agency finds and fixes the problems that stop search engines from crawling, rendering and indexing your site. Good ones do more than hand over a spreadsheet: they rank issues by revenue impact, write tickets your developers can act on or ship the fixes themselves, verify each fix in Search Console, and watch for regressions after every release. That last part is where most traffic is lost.
Q09Is it worth hiring an SEO agency?
It is worth it when the problem is bigger than your team's time or skills, and when the agency can prove its work. For technical SEO, ask three things: will you implement or only report, how will you verify each fix, and what happens when our next release breaks something. If you have a strong in-house developer and a small site, a one-off audit may be all you need. SEO audit services ↗
Q10How much does an SEO service cost?
It depends on site size, platform, how much is broken, and whether the agency implements fixes or only recommends them. A 50-page service site and a 200,000-URL store are different jobs. We do not list prices on service pages. Our US SEO cost guide shows typical market ranges and what drives them, and you get a fixed written scope after a short call. US SEO cost guide ↗
Q11How much does a SEO audit cost?
Audit prices vary with the number of URLs, the platform, and how deep the review goes: a crawl-only check is very different from one that includes rendering tests and server log analysis. Our SEO audit cost guide lays out the typical ranges and what each level includes. If you only need a one-time diagnosis, our SEO audit service is the right page. This page covers ongoing technical work. SEO audit cost guide ↗
Q12How long does technical SEO take to show results?
Fixes show up first in Search Console, as Google recrawls: fewer excluded pages, fewer errors, new URLs indexed. Rankings follow more slowly. Google says a site move can take a few weeks or more before new URLs replace old ones, and longer on big sites. Blocking bugs, like a stray noindex, can recover quickly once fixed. Our SEO timeline guide goes month by month. How long SEO takes ↗
Q13Does Core Web Vitals affect SEO?
Yes, but as one signal among many. Google says it recommends good Core Web Vitals "for success with Search" and that they align with what its core ranking systems reward. A fast page will not outrank a far more relevant one. Speed also decides whether visitors wait for the page at all, which is why we treat it as a revenue fix as much as an SEO one. Google: Core Web Vitals and Search ↗
Q14What is considered a good Core Web Vitals score?
Google's "good" thresholds are: Largest Contentful Paint (LCP, how fast the main content shows) within 2.5 seconds, Interaction to Next Paint (INP, how fast the page reacts to a tap or click) under 200 milliseconds, and Cumulative Layout Shift (CLS, how much the layout jumps) under 0.1. They are measured at the 75th percentile of real page loads, on mobile and desktop separately. web.dev: Web Vitals ↗
Q15What causes a poor LCP score?
The usual causes are a slow server response, a large hero image that is not compressed or not prioritized, render-blocking CSS and fonts, and main content that only appears after JavaScript runs. On ecommerce themes, the culprit is often a heavy image slider or an app script loaded before the product image. The fix starts by finding the actual LCP element on each template, then making it load first.
Q16How to pass Core Web Vitals assessment?
Measure real-user data first, from the Core Web Vitals report in Search Console or PageSpeed Insights field data, because lab scores alone do not decide the assessment. Then fix per template: speed up the LCP element, break up long JavaScript tasks to improve INP, and reserve space for images, ads and embeds to stop layout shift. Then use Validate fix in the report, which starts a 28-day monitoring session. Google: Core Web Vitals report ↗
Q17What is SEO in JavaScript?
JavaScript SEO makes sure pages built with frameworks like React, Vue or Angular can be crawled and indexed. Google processes JavaScript pages in three phases: crawling, rendering and indexing. Rendering happens later, in a queue. Google says server-side or pre-rendering is still a great idea, because it is faster for users and crawlers, and not all bots can run JavaScript. Google: JavaScript SEO basics ↗
Q18Is React still bad for SEO?
React is not bad for SEO. Client-side-only React is risky: if the server sends an empty shell and the content appears only after scripts run, search engines may index less, and many AI crawlers may see nothing. React rendered on the server, for example with Next.js, sends full HTML on the first request and is fine. The framework matters less than where the HTML is produced.
Q19Which JavaScript framework is best for SEO?
The best one is any framework that renders on the server or at build time: Next.js, Nuxt, Astro, SvelteKit or Remix all can. Google recommends server-side rendering, static rendering, or hydration, and calls dynamic rendering a workaround rather than a long-term solution. Pick the framework your team can maintain, then make sure every indexable page ships its content, links and metadata in the initial HTML. Google: Dynamic rendering as a workaround ↗
Q20What is SEO migration?
An SEO migration is any change that moves or rebuilds URLs in a way search engines must relearn: a new domain, a new platform such as Magento to Shopify, a switch to HTTPS, a new URL structure, or a redesign that renames pages. The SEO work is mapping every old URL to its best new match, redirecting it, and checking that Google picks up the new pages without losing traffic.
Q21How can I migrate my website without losing my SEO?
Crawl and save every current URL first, including ones that only exist in backlinks and analytics. Map each to its closest new page and use permanent server-side redirects, 301 or 308, in one hop. Keep redirects for at least a year, as Google advises. Update canonicals, sitemaps and internal links to the new URLs, then watch Search Console daily for the first weeks after launch. Google: Site moves with URL changes ↗
Q22How to do SEO for eCommerce?
On the technical side, ecommerce SEO is mostly about control. Faceted navigation (filters for size, color, price) can create millions of near-duplicate URLs, and Google says it will crawl many of them before learning they are useless. Decide which filters deserve indexable pages, block or canonicalize the rest, return a real 404 for sold-out-forever products, and keep Product markup matching the visible price and stock. Google: Managing faceted navigation ↗
Q23How to analyze a log file for SEO?
Export raw access logs from your server or CDN, keep only requests from search and AI crawlers, and verify Googlebot with a reverse DNS lookup, since many bots fake its name. Then compare: which URLs get crawled most, which never get crawled, how much crawling is spent on redirects, errors and parameter URLs, and how fast new pages are found. Logs show what bots did, not what they might do. Google: Verifying Googlebot ↗
Q24What is crawl budget, and does my site need to worry about it?
Crawl budget is how many URLs Google can and wants to crawl on your site. Most sites do not need to worry. Google's guide is written for large sites with over a million unique pages, sites with over 10,000 pages that change daily, and sites with many pages stuck as "Discovered, currently not indexed." If that is not you, fix indexing and duplicates instead. Google: Crawl budget guide ↗
Q25Is SEO dead now with AI?
No. AI search engines still depend on crawled, indexed web pages. Google says pages must be indexed and eligible to show with a snippet to appear as a link in AI Overviews or AI Mode, with no extra technical requirements. So a technically broken site is invisible to both classic search and AI answers. What is changing is what gets clicked, which is why citations now get tracked too. Google: AI features and your website ↗ Is SEO dead? The data ↗
Q26Can ChatGPT do SEO?
ChatGPT can draft titles, explain errors and write code for schema or redirect rules. It cannot see your Search Console data, crawl your site at scale, deploy fixes, or confirm that Google picked them up. Use it to speed up the work, and have a person check anything technical before it ships. A wrong robots.txt line written confidently by a chatbot can remove a whole site from search.
Q27Should I block AI crawlers in robots.txt?
Decide bot by bot, because they do different jobs. OpenAI says OAI-SearchBot decides whether you can appear in ChatGPT search, while GPTBot collects training data. Google says Google-Extended does not affect inclusion or ranking in Google Search. Anthropic and Perplexity also separate search bots from training bots. Blocking every AI bot with one wildcard can quietly remove you from AI answers. OpenAI: Overview of crawlers ↗
Q28Does technical SEO help you appear in AI Overviews?
It is the entry ticket. To be shown as a supporting link in AI Overviews or AI Mode, Google says a page must be indexed and eligible for a snippet, and there are no special AI files or markup required. Robots rules, nosnippet tags and noindex all limit what can be shown. Content and outside mentions decide whether you get picked, which is what our AI SEO service covers. Google: AI features and your website ↗ AI SEO services ↗
Q29Do you implement the fixes or just report them?
We implement them. FactoryJet builds Shopify, BigCommerce, WordPress, Webflow and Next.js sites, so the same team that finds a rendering bug or a redirect chain can open the pull request, ship it with your approval, and verify it in Search Console. If you have your own developers, we write the tickets for them and review their changes instead. Either way, a fix is not done until Google sees it.
Q30What is the difference between your SEO audit and technical SEO service?
The SEO audit is a one-time diagnosis of technical, content and authority issues, with a fix list in priority order. The technical SEO service is ongoing: we fix the technical items, check every release for regressions, handle migrations, and track crawl, index and Core Web Vitals data each month. Many clients start with the audit and move to ongoing work once they see the list. SEO audit services ↗
Find Out What Google Actually Sees on Your Site
Send us your site and the pages that matter most. We check crawling, rendering, indexing and speed on them, then tell you what we would fix first and who ships it. You get a fixed written scope before any work starts.