Service 06 / 14

Search, built into the site instead of added to it.

We build the site so search engines can read it, then use your own search data to decide which pages deserve to exist, and keep watching what changes.

In short

What this covers

Most SEO work is repair: a site built without it, then patched. We do it the other way round. The content model, the URLs, the templates and the structured data are designed for search from the start, so a new service page is already correct when it is written.

Then the work is driven by data you own. Search Console shows which queries already bring you impressions, which pages compete with each other, which ones are decaying. That decides the next pages, not a keyword list bought by the thousand.

Usually for
Service businesses whose site does not show up for what they sell, Companies redesigning a site that ranks today and cannot afford to lose it, Teams with search data and no time to read it

The work

What we do

  • Technical audit

    Indexability, sitemaps, redirects, canonicals, speed, structured data, read the way a crawler reads them. Try it on your site.

  • Search data

    Search Console queries, pages and positions, joined to the site’s own pages to find gaps, cannibalization and decay.

  • Intent

    Queries sorted into commercial, local, informational and navigational, so the pages that can bring a customer come first.

  • Architecture

    One page per service that deserves its own answer, and territory pages only where you really work and have something specific to say.

  • Links and schema

    Internal links from the content graph, and structured data for the business, its services and its questions.

  • Monitoring

    Index coverage, sitemaps and the queries that move, checked on a schedule, with a short note when something needs a decision.

Architecture

How the system fits together

One loop, run on your data. Every step can be checked: each recommendation carries the query, page or file that produced it.

  1. Technical audit

    The site read as a crawler reads it: status codes, robots, sitemap, canonicals, structured data, headings.

    site/server/growth/audit

  2. Search data

    Queries, pages, clicks and positions from Search Console, kept as dated snapshots.

    Search Console API

  3. Analysis

    Opportunities (impressions without clicks), cannibalization (two pages on one query), decay (losses period over period).

    site/server/growth/seo.js

  4. Architecture

    Services × territories × questions, checked against what exists, so a gap is a missing answer, not a missing keyword.

    Content model

  5. Build

    Pages, links and markup generated from the content model, audited before release.

    Static generator

  6. Monitor

    Sitemaps and index status checked on a schedule; changes summarised for a person.

    Companion Worker (cron)

Rankings are an outcome we report, never a promise we make.

Status

What runs today, and what waits for access

Live means it runs now. Integration-ready means the code, the data model and the tests exist and it starts once your account or a platform approval is connected. Planned means not running yet: designed, or built and tested but not yet connected to a live endpoint.

  • Live

    Technical audit

    Runs now at /audit/: 41 checks, each with its evidence.

  • Live

    Content model, schema and sitemap generation

    The system this site is built on.

  • Planned

    Search Console analysis

    Opportunity, cannibalization and decay analysis is built and tested; the job that runs it on your Search Console data is not built yet.

  • Planned

    Scheduled monitoring

    The schedule is declared in the companion Worker; the job that reads Search Console on it is not built yet.

Integrations

What it connects to

Google Search Console
Search analytics, sitemaps and URL inspection (quota-aware: URL inspection is limited per site per day, so it runs as a queue).
Google PageSpeed Insights Integration-ready
Lighthouse lab data for performance and accessibility in the audit.
IndexNow Live
Tells participating search engines when pages change.

Measurement

What we measure, and where the number comes from

Impressions and clicks per page and query
Search Console, dated snapshots, compared period over period.
Index coverage
Sitemap submissions and URL inspection results.
Leads from organic search
The attribution engine: organic search as the channel of the first or last touch of each lead, not a share of traffic.

Handover

What you end up with

  • A technical audit with the evidence for every finding
  • A page plan: services, territories and questions, each with the data behind it
  • Redirect map and checks for any migration
  • Monitoring notes when something changes

Limits

Where this isn’t the right fit

We don’t promise rankings, positions or traffic. Search engines decide; we make the site easy to read and worth showing, and report what happens.

No link buying, no pages written for keywords nobody asks about, no city-swap pages.

We have not run SEO for a client yet. The audit and the system behind this site are what you can check today.

Stack

Tools we reach for

  1. Search Console API
  2. Structured data (schema.org)
  3. XML sitemaps
  4. IndexNow
  5. PageSpeed Insights
  6. Static site generation

How we build it This site is its own test case: titles, descriptions, structured data, sitemap and internal links are generated from one content model, and an SEO audit runs on every build and blocks a release with broken links or orphan pages. How this site is built

FAQ

Questions about this

All questions

Will the site rank well?

Nobody can promise rankings. What we can do is build the parts we control properly: content in the HTML, one clear topic per page, structured data that matches the page, internal links, redirects from old URLs, and fast pages.

Do you guarantee rankings, leads or AI citations?

No. Search engines, ad platforms and AI assistants decide what they show, and anyone who guarantees a position is guessing or buying something they shouldn’t. We build what we control properly, measure what happens with stated methods, and report it, including when it doesn’t work.

Whose accounts do you use?

Yours. Your Google Business Profile, ad account, Search Console, phone numbers and data stay in your name, and we get access you can remove at any time. Some connections also need an approval from the platform (Google reviews API access to Business Profiles, for example); until then the same work is done by hand, from the same rules.

Want to know what search sees first?

Run the audit, or tell us about the site and we’ll look at the data with you.