Contact

Send the URL, what changed, and the exact symptom

The more specific the symptom, the faster I can tell whether this fits a fixed first sprint.

Useful examples: Google Ads conversions are not firing, product pages are crawled but not indexed, cold TTFB is 10s+ but cached pages are fast, Cloudflare is blocking Googlebot or users, or a migration launched and traffic dropped.

Response and privacy

Most inquiries get a reply within 1 business day, and nearly all within 2, with a bounded first-step recommendation when the issue is in lane.

Inquiry details are only used to review fit and reply. No mailing list, no resale, and no sharing outside the project.

Name

Website URL

Affected URLs / conversion paths (optional)

Issue type

Pick the lane first so the form can ask for the minimum useful follow-up context.

CMS / stack (optional)

Exact symptom

Useful details: what is not firing, not indexed, too slow, blocked, dropped, duplicated, or mismatched. Keep it specific enough to test.

What changed recently

GSC state, if known

Tracking/tools involved

Access available (optional)

Budget/timeline range (optional)

Indexing follow-up

Affected URLs or page types

GSC state or coverage message

Speed follow-up

Representative URL

Device focus

What changed right before the regression

Cloudflare follow-up

Error code

Affected path or URL

When it started

Migration follow-up

Launch date

Old platform

New platform

SEO Ops follow-up

Sites in scope

Current tool stack

Where the workflow breaks

Other follow-up

Closest symptom or lane

Where it shows up

Evidence files

Upload screenshots, exports, PDFs, logs, or dashboard exports. Up to 5 files, 12 MB each.

By submitting this form, you are sharing project details only for fit review and reply. Read the privacy note.

The best submissions include

Website URL.
Affected URLs, page types, forms, or conversion paths.
The exact symptom instead of a broad category.
CMS / stack.
What changed just before the issue showed up.
GSC state, tracking tools, access level, and budget/timeline range if available.

The likely path

Review the issue and the context you send.
Define the cleanest bounded sprint if the problem is a fit.
Implement, verify, and hand off the result clearly.

Not sure what to send?

Use a sprint input checklist when the issue is specific but the supporting context is scattered.

Technical SEO / GSC / crawl issues

10-URL Technical Sanity Scan

A quick directional scan for one specific technical SEO, tracking, indexing, speed, or access issue. It is not a free full audit or implementation promise.

A useful output is: this looks like a lane, the likely first failure path is a hypothesis, and a proper first sprint would cover a defined scope.

Pricing expectations

Most work starts as a fixed first sprint after the issue is reviewed.

Small diagnostics usually start around $350.
Focused technical SEO, tracking, indexing, or speed sprints commonly land between $650 and $1,500+.
Larger implementation or recovery work is scoped separately once the first failure path is clear.
If you need a $99 SEO audit, this is not the right fit.
If something technical is suppressing indexing, speed, crawl, tracking, or rollout recovery, send the URL, what changed, and the exact symptom.