Core SEO service
Technical SEO that makes important pages crawlable, indexable and fast
You receive
- Technical findings report
- Prioritized fix list
- Developer-ready tickets
- Redirect and canonical maps
- Validation checklist
Scope, timeline and price confirmed in writing before work starts.
The service
What technical SEO covers
Technical SEO covers the infrastructure of search visibility: how URLs are discovered, which ones crawlers are allowed to fetch, how pages render, which version a search engine treats as canonical, and how quickly content loads for real users. Problems at this layer are often invisible in a browser, yet they can quietly cap the performance of your content, links and brand.
We combine crawl data, Google Search Console reports, raw-versus-rendered HTML checks and, when available, server logs. Every finding is tied to evidence (the affected URLs, how we confirmed the issue and what the fix should look like) so your developers can act on it without guesswork.
Business problems
Problems this service addresses
Important pages aren't indexed
Search Console's page indexing report lists key URLs as “Discovered - currently not indexed,” “Crawled - currently not indexed” or as duplicates, and nobody is sure why.
Traffic dropped after a release
A template change, robots rule, redirect update or rendering change shipped, and organic sessions fell soon after.
Duplicate and parameter URLs
Filters, tracking parameters, trailing slashes or protocol variants split signals across many versions of the same page.
Content depends on JavaScript
Key copy, links or product data appear only after client-side rendering, and Google notes that “not all bots can run JavaScript.”
Source: Google Search Central: Understand JavaScript SEO basics
Slow templates and weak Core Web Vitals
Real-user data shows slow Largest Contentful Paint, layout shifts or sluggish interactions on the templates that matter most.
Crawl activity spent on the wrong URLs
On larger sites, bots spend time on faceted, paginated or low-value URLs instead of new and updated pages.
What we do
The work involved
- 01
Crawlability and indexability analysis
A full crawl compared against your XML sitemaps and Search Console indexing data to find pages that are blocked, orphaned, excluded or indexed unintentionally.
- 02
Robots.txt and XML sitemap review
We confirm robots.txt blocks only what it should, sitemaps list canonical, indexable URLs that return 200, and both are referenced and submitted correctly.
- 03
Canonical tags and duplicate URL management
We map duplicate clusters (parameters, letter case, trailing slashes, protocol, pagination) and make sure canonical tags, internal links and redirects all agree on one preferred URL.
- 04
HTTP status codes and redirect chains
We find 4xx and 5xx responses, soft 404s, redirect chains and loops, and recommend permanent redirects straight to the final URL, in line with Google's advice: “Avoid chaining redirects.”
- 05
JavaScript rendering and indexable HTML
We compare the raw HTML response with the rendered DOM to confirm that main content, links, metadata and structured data are available to crawlers without relying on client-side execution.
- 06
Internal linking and site architecture
We measure click depth, orphan pages and how internal links support commercial pages, then propose navigation, breadcrumb and contextual link changes.
- 07
Structured data and Schema.org
We validate existing markup against Schema.org and Google's structured data guidelines, including “Don't mark up content that is not visible to readers of the page,” and recommend only the types your content genuinely supports.
Source: Google Search Central: General structured data guidelines
- 08
Core Web Vitals and performance
Google describes Core Web Vitals as “a set of metrics that measure real-world user experience.” We review that field data from the Chrome UX Report alongside lab tests to locate LCP, INP and CLS problems by template and identify their likely causes.
Source: Google Search Central: Understanding Core Web Vitals
- 09
Pagination and faceted navigation
We decide which filter and sort combinations deserve indexable URLs and how the rest should be handled with links, canonicals or crawl controls.
- 10
Website migration risk assessment
Before a redesign, replatform or domain change, we identify the URLs, redirects and templates most likely to cause traffic loss.
- 11
Log-file analysis
When server logs and access are available, we analyze how search engine bots actually crawl the site: which sections get attention, which are ignored and where crawl activity is wasted.
Inside the work
What two common findings look like
Before: three requests to reach the page
After: one permanent redirect
<body> <div id="root"></div> <script src="/app.js"></script> </body>
<body>
<div id="root">
<h1>Patient intake software</h1>
<p>Reduce front-desk time…</p>
<a href="/pricing/">Pricing</a>
</div>
</body>Illustrative example · fictional page
Source: Google Search Central: Understand JavaScript SEO basics
Crawl controls
Reading a robots.txt file the way a crawler does
User-agent: * Disallow: /cart/ Disallow: /search? Allow: / Sitemap: https://www.example.com/sitemap.xml
Disallow: /cart/Keeps crawlers out of session-specific pages with no search value.
Disallow: /search?Stops internal search results from generating endless crawlable URLs.
Sitemap:Points crawlers to the list of canonical URLs you want indexed.
- robots.txt manages crawling; Google says it “is not a mechanism for keeping a web page out of Google.” To keep a page out, “block indexing with noindex or password-protect the page,” and for
noindexto work, “the page or resource must not be blocked by a robots.txt file.” Private pages always need real access control.Sources: Google Search Central: Introduction to robots.txt; Google Search Central: Block search indexing with noindex
Illustrative example · fictional site
Deliverables
What you receive
Technical findings report
Each issue with affected URLs, supporting evidence, business impact and the recommended fix.
Prioritized fix list
Issues ranked by expected impact, effort and risk, so the team knows what to do first.
Developer-ready tickets
Specifications with acceptance criteria, formatted for Jira, Linear, GitHub Issues or a shared spreadsheet.
Redirect and canonical maps
Where needed, source-to-target URL mappings ready for implementation and testing.
Validation checklist
How to confirm each fix after release using crawl data, rendered HTML checks and Search Console.
Walkthrough session
A working session with your marketing and engineering leads to review findings and answer questions.
Measurement
How success is measured
- Indexing coverage
- Share of priority URLs indexed under the intended canonical, tracked in Search Console's page indexing report.
- Crawl health
- Fewer errors, redirect chains and non-canonical internal links in recurring crawls.
- Core Web Vitals
- Share of URLs passing LCP, INP and CLS thresholds in field data, grouped by template.
- Landing-page performance
- Impressions, clicks and conversions for the affected page groups after fixes are deployed.
Who it's for
Who benefits most
- Sites with indexing problems that new content hasn't solved
- Teams preparing for a redesign, replatform or domain change
- JavaScript-heavy sites built with React, Next.js, Vue or similar frameworks
- E-commerce and marketplace sites with faceted navigation
- Companies with in-house or agency developers who need clear specifications
Questions
Technical SEO FAQ
Do you implement the fixes yourselves?
We write specifications and tickets and work alongside your developers, including reviewing changes on staging. Hands-on implementation can be scoped separately, depending on your platform and the access you can provide.
Which tools do you use?
Typically a desktop crawler, Google Search Console, Chrome DevTools, PageSpeed Insights and Chrome UX Report data, Google's Rich Results Test, and log analysis tools when logs are available. The exact set depends on your stack and data access.
Will fixing technical issues increase our rankings?
Technical fixes remove obstacles; they don't guarantee rankings. Outcomes depend on content quality, competition and how quickly fixes are deployed. We agree on measurable indicators up front so you can see what changed.
How long does a technical SEO review take?
It depends on site size, complexity and data access. We confirm the timeline in writing during scoping, before any work begins.
Get started with Technical SEO
Tell us about your website and what you need from Technical SEO. We'll review it and reply with an honest view of the opportunity and a proposed next step.
What happens next
We review your site and request
A person on our team looks at your website and the problem you described. You won't receive an automated report.
We reply within two business days
By email, with initial observations, any questions we have, and whether we think we're a good fit.
Scoping call and written proposal
If it makes sense to continue, we schedule a call and send a written scope, timeline and price. Nothing is billed before you approve it.