You published the pages. You can open them in your browser. Google either does not list them, lists the wrong version of them, or shows them below pages that say less than yours does. Nobody on your team can say why, because the fault is rarely on the page you can see. It sits in a sitemap, a redirect, a tag in the page head or a single line in robots.txt.
Technical SEO services are the work of finding that fault and fixing it. Our SEO audit looks at the whole site; this page covers the technical layer, which is the first layer of our organic SEO services.
01What a technical SEO audit checks
A technical audit answers one question per area: can Google reach this page, understand it, and trust it enough to show it? Eight areas cover almost every case we see. Each one has a free first check you can run yourself.
| Area | The question it answers | Where to look first |
|---|---|---|
| Crawl access | Can Googlebot fetch the page, or does robots.txt or a login stop it? | yourdomain.com/robots.txt |
| Indexing | Is the page stored by Google, and if not, what reason does Google give? | Search Console, Page indexing report |
| Canonicals | Does each page name itself as the preferred address, and does Google agree? | View source, search for rel="canonical" |
| Redirects | Do sitemap and internal links point at addresses that answer directly? | The sitemap, ten URLs at a time |
| Speed and Core Web Vitals | Do real visitors get a fast, stable page on a phone? | Search Console, Core Web Vitals report |
| JavaScript rendering | Is the main text and every link present after Google renders the page? | URL Inspection, view the rendered page |
| Structured data | Does the markup match what a visitor can read on the page? | Google's Rich Results Test |
| AI crawler access | Have you decided, on purpose, which AI crawlers may fetch the site? | robots.txt and your host or CDN settings |
Google's own guidance backs the order. Its JavaScript documentation describes three phases, crawling, rendering and indexing, and says Googlebot checks robots.txt before it requests a page. A fault in an early phase hides everything after it.
02What we fix first, and why
We fix in the order that releases the most pages for the least work: anything that stops a page being indexed, then anything that sends Google to the wrong address, then speed and markup. Speed and structured data are worth doing, but they improve a page Google already holds. They do nothing for a page it never stored.
Remove blocks and wrong tags
Lift any robots.txt rule or noindex tag on pages that should rank. Google's robots.txt guide says the file is not a way to keep a page out of Google, so a noindex tag or a password is the right tool for pages you want hidden.
Make every address answer once
Each page gets one address that returns a normal page directly, used the same way in the sitemap, the internal links and the canonical tag.
Repair rendering
Make sure the main text and the navigation links exist in the page after Google renders it. Google states that it can only discover links written as standard HTML links with an href attribute.
Fix speed and markup last
Bring slow templates into the good range and correct structured data that disagrees with the visible page.
03Worked example: a sitemap that lists redirecting URLs
This is the fault we find most often on sites that have 'pages that never get indexed'. A sitemap is a list of the addresses you want Google to show. Google's sitemap guide says to list the canonical address and to write every URL out in full. When a sitemap lists addresses that redirect, every one of those entries points Google at a page you are telling it not to keep.
How to spot it in five minutes
Open the sitemap
Go to yourdomain.com/sitemap.xml and copy ten addresses from different page types: a service page, a blog post, a category, the homepage.
Test each address
Paste them into a free redirect checker, or run curl -I followed by the address. You want a plain 200 answer. Any 301, 302 or 308 is a fail.
Compare with the canonical
Open one page, view source, search for canonical, and check the address matches the one in the sitemap character for character.
Check Search Console
In the Page indexing report, open the Page with redirect group. If your sitemap addresses are in it, the sitemap is listing redirects.
04Page speed and Core Web Vitals: the numbers Google publishes
Core Web Vitals are three measurements of how a page feels to a real visitor. Google's web.dev guide sets the good range for each at the 75th percentile of page loads, split by mobile and desktop, which means three out of four visits must meet it.
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How fast the main content loads | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How fast the page reacts to a tap or click | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less |
Source: web.dev, Web Vitals (web.dev/articles/vitals).
The Core Web Vitals report in Search Console uses field data from real visitors and groups similar pages together, so it shows site-wide patterns, not the state of one URL. We use it to find the one template that is slow for a hundred pages, which is a single fix.
05AI crawler access in robots.txt
AI search products fetch your pages with their own crawlers, and many hosts and CDNs block some of them by default. Whether to allow each one is your decision, and it should be a decision rather than an accident. We read robots.txt and your host settings together, list which crawlers are allowed, and ask you which you want.
Google's AI features guide says AI Overviews and AI Mode have no extra technical requirements beyond being indexed and eligible to show with a snippet, and that no special markup or AI text file is needed. So the technical work for those features is the same as for ordinary search. Our AEO services cover the content side of being named by AI answers.
06How technical SEO work runs with us
We crawl and read your data
We crawl the live site, read your Search Console reports and list every fault with the pages it affects.
We rank the fixes
Each fix gets an effort rating and an owner: your developer, your host, or us. The list is ordered by how many pages each fix releases.
We fix or brief
Where we have access, we make the change. Where we do not, we write a ticket your developer can act on without a call.
We re-check the live site
After each fix we test the live address, not the staging copy, and watch the Page indexing report for the affected group.
07What you get at the end
- A ranked fix list with the pages each fix affects, the owner and the effort.
- A clean sitemap, canonical and redirect map that all use one address shape.
- A robots.txt and crawler-access decision you approved in writing.
- A speed report showing which templates miss the three thresholds above.
- Developer-ready tickets for every fix we do not make ourselves.
- A before and after view of the Page indexing report.
Technical work is where our SEO content services and link building start. A page Google cannot index cannot gain from either. For the full list of what each fix covers, see our organic SEO checklist.
This suits you if
- Important pages show as not indexed, or Google lists an old or wrong address.
- You moved or rebuilt the site and traffic fell afterwards.
- Your developer says the site is fine but Search Console disagrees.
- Your site relies on JavaScript to show its text.
Skip it if
- Every key page is indexed and ranks, and your gap is content or links. Start with <a href="/seo-audit-services/">an audit</a> instead.
- You have fewer than a few pages and no redirects. Fix the basics with Google's SEO starter guide.
08Technical SEO by moment: what to check when something changes
What a typical technical SEO service gives you
- A scored report with hundreds of warnings and no order
- Fixes listed with no page counts
- Speed work before indexing work
- A PDF handed over, with nobody owning the tickets
- A one-off check, then silence until the next problem
What we do instead
- A ranked list: indexing first, then wrong addresses, then speed and markup
- Every fix with the number of pages it affects
- Developer-ready tickets, each with a test
- A re-check of the live site after each change
- Technical work inside the same $2,000 a month
Most technical faults appear at a moment of change, not at random: a redesign, a move to a new platform, a new domain, a batch of new pages or a plugin update. Knowing the moment tells you where to look first. Agencies list the same moments as the times to hire help: unexplained low traffic, a redesign, a platform migration and growing complexity.
| The moment | What usually breaks | Check before launch | Check after launch |
|---|---|---|---|
| A redesign | Page addresses, titles and internal links change | List every old address and its new address | Compare indexed page counts for your main templates in the Page indexing report |
| A move to a new platform | Redirects, canonical tags and sitemaps are rebuilt wrongly | Test the redirects from old to new on a staging copy | Open the sitemap, test a sample of addresses, then request indexing for the top pages |
| A new domain, or a www change | Two versions of the site answer | Choose one version and redirect the other in a single step | Check that every old address reaches the new one without a chain |
| A new batch of pages | Pages with no internal links, or with the wrong canonical | Link each new page from an existing page | Check each page is indexed after a week |
| A plugin or theme change | Robots tags and structured data output change | Compare page source before and after on one page per template | Re-check a sample of templates |
Ten Speed, best technical SEO agencies, for the list of moments
A new batch of pages and a platform move are the two moments where a ranked fix list pays for itself fastest. Our SEO audit services are built to run at exactly these points.
09How to write a fix as a developer ticket that gets done
Technical SEO often fails at the handoff: a correct finding written so vaguely that a developer cannot act on it. A ticket that gets done names the URL pattern, what happens now, what should happen, how to test it and why it matters.
Every ticket carries these six things
0 of 6 done10What technical SEO costs, and what moves the price
Technical SEO has no single price because the work depends on the site and not on the service name. One large US agency publishes audits from $8,600 for up to 70 pages, while its own pricing guide gives $650 to $1,500 for sites under 50 pages. That is a tenfold spread, and scope explains it.
| Driver | Why it changes the work | Ask yourself |
|---|---|---|
| Number of pages and templates | Fixes apply per template and checks apply per page | How many page types does my site have? |
| Platform and code access | A closed site builder limits what can be changed | Who can edit templates, redirects and robots.txt? |
| Languages and countries | Each version needs its own checks | How many versions of each page exist? |
| Development time | Someone must make each change | Do I have a developer, or does the provider make the changes? |
| Reporting and approvals | Slow sign-off stretches the work | Who approves a change, and how fast? |
WebFX, SEO audit services; Nathan Ojaokomo, best organic SEO agencies, for the cost drivers
In our plan technical work sits inside the flat $2,000 a month, next to the pages, links and reporting. The packages page lists everything included.
