Skip to content

SEO

The SEO problems you can't write your way out of

The layer content cannot compensate for. If Google cannot crawl a page, cannot index it, or renders it as an empty shell, the quality of what is written on it is irrelevant. This page is for sites already publishing decent content that is not ranking — because that is usually a technical problem wearing a content problem's clothes.

How it runs

What actually happens, in order

  1. Crawl the site the way a search engine does

    Week 1

    Every URL, with response codes, redirect chains, canonical tags, indexability and internal link depth. The output is a list of specific faults with specific URLs, not a score out of a hundred.

  2. Compare what is indexed to what should be

    Week 1

    Search Console coverage against the crawl. The interesting cases are pages you want indexed that are not, and pages that are indexed and should not be — tag archives, filtered listings, staging copies, and search result pages competing with the real ones.

  3. Check what renders without JavaScript

    Week 1

    Some sites deliver their main content only after JavaScript runs. Google can handle that, less reliably and more slowly than it handles HTML. If your product descriptions are not in the page source, that is worth knowing.

  4. Core Web Vitals, from field data

    Week 2

    The Chrome UX Report shows what real visitors experienced, which is the data Google uses. Lab tools like Lighthouse are diagnostic — they tell you why, on a simulated connection, but they are not the measurement being graded.

  5. Fix, then verify it took

    Weeks 2–5

    Changes implemented and re-crawled, with Search Console watched to confirm the pages actually entered the index. An audit that ends with a document is half a job.

Scope

What is included — and what is not

Both lists, because the second one is where projects go wrong and almost nobody publishes it.

  • Full crawl with every fault tied to specific URLs
  • Index coverage reconciled against the crawl
  • Redirect chains and loops mapped and flattened
  • Canonical, hreflang and pagination handling corrected
  • Structured data implemented and validated
  • Core Web Vitals work based on field data, not lab scores
  • XML sitemap and robots.txt rebuilt to match reality
  • Re-crawl and Search Console verification after the fixes
  • Content writing, which is a separate service — though we will tell you which pages are thin
  • Link building
  • Changes on platforms that do not permit them, such as some hosted store builders, where we will tell you what is impossible rather than bill to attempt it

Straight answers

Questions people actually ask

I publish good content and it does not rank. Why?
Most often one of: the pages are not indexed at all, they are competing with other pages on your own site for the same term, internal linking buries them four clicks deep, or the site is slow enough on mobile that engagement never establishes. All four are diagnosable in an afternoon, and none of them are fixed by writing more.
Is my site slow enough to matter?
Check the Core Web Vitals field data rather than a Lighthouse score. Speed is a real but modest ranking factor and a very large conversion factor. The reason to fix it is usually the visitors leaving, not the ranking position.
What is keyword cannibalization and do I have it?
Two or more of your pages targeting the same search, so Google alternates between them and neither builds authority. It is common on sites with both a service page and several blog posts on the same topic. The fix is consolidation and internal linking, not deletion.
Do I need structured data?
For a local business, yes — it is how Google reads your address, hours and services with certainty rather than inference. It does not directly raise rankings, but it affects how your result looks, and a result that shows hours and reviews gets clicked more than one that does not.
Can you do this on Wix or Squarespace?
Partly. Metadata, structure, internal linking and content are all controllable. Server response time, some redirect handling and certain structured-data implementations are not. We will tell you which of your problems are fixable on your platform before you pay to find out.

Start with the free audit. It takes two seconds and it is honest about what it cannot see.