Crawl and index audit
Every URL on the site sorted into indexed, left out on purpose, or left out by mistake, using a full crawl and Search Console’s indexing report. You receive: an index map and a fix list, worst first.
Technical SEO services
We find what stops Google from reaching, storing and quickly loading your pages, fix it with your approval, and log each change against your Search Console.
Get your technical SEO checkWhat technical SEO is
Technical SEO services fix what keeps Google from finding, reading and loading your pages.
Googlebot has to reach the page by following links. We check your robots.txt, internal links and server responses so every page that earns money is reachable.
Reaching a page is not storing it. Search Console lists each page Google left out and why, and we sort those into fix, leave or remove.
Speed, layout shifts and response to a tap are measured on real visits from phones, then fixed template by template.
How the work is done
Technical SEO usually starts with an audit. What differs is what happens after it.
| Audit onlyFindings you hand on | Audit and fixesFindings that ship | |
|---|---|---|
| What you receive | A report listing the issues found | A ranked fix list, then a change log as each fix goes live |
| Who makes the change | Your developer or another vendor | We write it with your developer or in your CMS, and you approve it first |
| How a fix is checked | Checked at the next audit | Re-crawled after release and re-measured in Search Console |
| Best when | You have a developer ready to work from a list | You have no in-house developer time for SEO fixes |
| Starting cost | A one-time audit, $750 to $1,500 with us | Part of SEO, from $2,500 a month |
The audit is written so your developer or any other agency can use it without us. If you’d rather have the fixes made, they continue from the same list.
The rules
Six points from Google Search Central and web.dev that decide what we fix and what we leave.
Google’s guide is for sites with over a million pages that change weekly, or over 10,000 pages that change daily, or for sites with many URLs reported as Discovered, currently not indexed. It says these are rough figures and that others needn’t read it. So we start with indexing, and look at budget only if your site fits.
Google says robots.txt is not a way to keep a page out of search. A blocked URL can still appear, without a description, if other pages link to it. The tools Google names are a noindex tag or a password, so we use those for pages that must stay out.
Those are the limits for Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, measured at the 75th percentile of page loads. We report all three from real visits, and treat a lab test as a rough guide.
A sitemap file is limited to 50,000 URLs or 50MB uncompressed. Google uses the last-modified date only if it is consistently and verifiably accurate. So we list the pages you want indexed and set the date from real edits.
Google says its indexing system uses a permanent redirect as a signal that the target should be the canonical URL, and does not do so for a temporary one. In a migration, each old page gets a permanent redirect to its closest new page.
Google’s policy says not to mark up content readers can’t see. A violation can lead to a manual action, which removes the page’s eligibility for rich results. Our markup is written from the visible page and tested before release.
The scope
From the crawl audit to redirects, each part ends in a logged change or a document.
Every URL on the site sorted into indexed, left out on purpose, or left out by mistake, using a full crawl and Search Console’s indexing report. You receive: an index map and a fix list, worst first.
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift measured on phones from real visits, then fixed template by template. You receive: the three numbers before and after each release.
JSON-LD written from what each page visibly says, such as a local business, an article, a product or a breadcrumb, and tested before release. You receive: the markup, and a validation result for every template.
Click depth mapped, orphan pages found, and links added so the pages that earn money sit close to the home page. You receive: a structure map and the list of links to add.
A robots.txt, an XML sitemap and noindex tags that agree with each other, plus a check of which crawlers your robots.txt lets in. You receive: the files, and the reason for every rule.
A redirect from each old URL to its closest new page before a redesign or platform move goes live, then a check for chains and broken links. You receive: the redirect map and a post-launch crawl.
How it runs
Each step leaves a document you can open, and nothing changes on your site without your approval.
Crawl summary
| Group | URLs | Action |
|---|---|---|
| Pages worth indexing | 168 | Keep |
| Tag, author and date archives | 231 | Add noindex |
| Tracking-parameter duplicates | 142 | Point to the clean page |
| Redirects | 61 | Check for chains |
| Broken URLs (404) | 38 | Redirect or remove |
Our stack
Crawlers, speed tests and Google’s own reports. Each is listed with what it checks.
Screaming Frog is a desktop crawler that lists every URL on a site with its status code, title, canonical and links.
We crawl the full site to find broken links, redirect chains, duplicate pages and orphans, and crawl again after every release.
How the engagement runs
Technical SEO isn’t a one-time cleanup. Any release can undo a fix, so the work runs for as long as the site keeps changing.
We crawl the whole site the way Googlebot does and, where you give us access, read the server logs to see what it really fetches and what it never reaches. That is reconciled with Search Console’s indexing report, Core Web Vitals from real phone visits and a structured data check. Every URL is sorted before a single fix is proposed, and the phase ends with one ranked list, worst first, each fix scoped by effort and by the pages it touches.
We work down the list: clear duplicate and parameter URLs with canonicals and noindex, recover pages Google left out, bring Core Web Vitals inside Google’s limits on phones, and release structured data that matches the page. Each change is made with your developer or in your CMS, approved by you, and checked so a fix in one template doesn’t break another.
Any deploy can bring a fixed problem back. We watch indexing, Core Web Vitals and crawl health between releases, and check a redesign or migration on a staging copy before it goes live. You see the same numbers we do, in your own Search Console.
Reported monthly, from your own Search Console, against the starting numbers recorded before the first change.
Our commitment
Technical work is easy to hide behind jargon. These are the terms you can hold us to.
Your accounts stay yours
Search Console, analytics, the domain and your hosting stay in your name. We work through the access you grant, and you can remove it whenever you choose.
One senior strategist
The same senior strategist owns your technical roadmap from the first crawl onward, and answers for every change that ships.
Bad news first
If a release breaks something or a fix doesn’t hold, you hear it from us first, the same US business day, with what we’re doing about it.
Nothing renews on its own
The scope is written down before work starts, and nothing renews on its own. Ask a question and a senior strategist replies within 4 hours.
If the crawl finds nothing worth fixing, we’ll tell you that too.
Questions
Keep exploring
Find out which AI answers name your business, and fix what’s missing.
More booked calls from the map pack, tagged by source.
What to fix first, ranked by effect and effort.
Earned links from sites your clients read, each one logged.
Category and product pages built for search, reported in revenue.
Senior advice for in-house teams, in writing.
The profile, five pages and listings a small business needs first.
SEO for large sites, run through your tickets and releases.
SEO for agencies to resell under their own name.
Start here
Tell us your site address and what it’s built on. We’ll crawl it, compare it with what Google has indexed, and send back a dated check with what to fix first.