quietmason
Technical SEO

Technical SEO consultant for sites that cannot afford guesswork

We work from your own Search Console data (what is crawled, what is indexed, what people actually search), then fix the blockers and re-measure so you can see the difference.

Technical SEO. Audit from $400 · remediation scoped per finding — based on your own Search Console data. Delivery 2–5 days for an audit. Reply within one business day.

Where we start

Most "why is my website not ranking" answers are boring and checkable: pages excluded from the index, a canonical pointing at the wrong host, client-side rendering that hides the content, duplicate titles across a template, internal links aimed at pages nobody wants. We audit those first, in that order, because they are the ones that move.

Crawl & indexing

Coverage per page, robots and meta directives, sitemaps, canonical host, redirect chains, soft 404s, pagination.

Rendering & speed

Core Web Vitals on real URLs, image and font weight, render-blocking assets, layout shift from ad or consent scripts.

Meaning & structure

Structured data that matches the visible page, heading order, internal linking between related pages, entity consistency.

What you get

  • A findings list with severity, effort and the fix for each item — no filler
  • The fixes applied where you want us to apply them, or a patch list if your team prefers
  • A before/after read from Search Console and PageSpeed-style measurements
  • Wording we are willing to defend: no "we improved your SEO score" without a number attached

Audits from $400. Remediation is scoped per finding, so you can take the fix set in stages. Monthly measurement is optional and cancelable. We do not sell backlinks, and we will not pretend to.

What we need from you

Read-only access to Search Console, the site URL, and one sentence on the commercial goal. If you already have a report you do not trust, send it: we will say which parts hold up.

Related

Usually looked at together

Automation & pipelines

When the fix needs data collected and kept current rather than a one-off edit.

AI search visibility

The same markup and entity work that gets a page quoted rather than skipped.

Selected work

How we describe systems we built and maintain.

Questions

Common questions

  • What do I actually get at the end? A written audit: every finding, the evidence for it, the impact, and the order to fix it in — plus the before-and-after from your own Search Console once work is done.
  • Do you need access to my Search Console? Read access, yes: it is where your real index coverage lives. If you would rather not grant it, we say up front what the audit can and cannot conclude without it.
  • Will you implement the fixes, or just list them? Either. The audit stands alone; remediation is scoped per finding, highest impact first, and is a separate decision you make with the list in hand.
Deliverables

What ships, in order

An audit is not a tool export. It is a written punch list your developer can start on Monday morning, with the raw data behind every recommendation, so a second opinion can check our work.

1. Crawl report

Every URL with status code, title, meta, H1 count, canonical, schema types, internal inbound links and word count: the spreadsheet other findings hang off.

2. Indexing snapshot

Your own Search Console coverage: what is indexed, what is excluded and why, and recent crawl errors, not a third-party guess.

3. Core Web Vitals pass

Lighthouse per page template, mobile and desktop, with the gap to the target and which change closes it.

4. Structured data check

What is declared, whether it matches the visible page, and which types are missing for the pages that should carry them.

5. Prioritized fix list

P0 / P1 / P2 with an effort estimate and a recommended order, so the cheap high-impact half gets done first.

6. AI-visibility baseline

Your buyers' questions run against the answer engines, recording who gets named and cited before we change anything: the "before" number.

Plus a written handover so the next person does not have to reverse-engineer the findings: what we checked, what we concluded, and what we left alone.

A note on honesty: schema and FAQs do not buy citations by themselves. A 1,885-page study (Ahrefs, 2026) found adding JSON-LD produced no measurable citation lift on any platform. Markup earns eligibility; answering the question earns the citation. We say that so you can ignore anyone promising the opposite.