Honest Answers to Real Questions

We examine how search engine crawlers access and navigate your site, how fast your pages load, whether your indexation signals are configured correctly, how your structured data is implemented, and whether your HTTPS configuration is complete. The exact scope depends on your site's architecture. A content-heavy blog has different priorities than an e-commerce catalog.

For most audits, we need read-only access to GSC and ideally GA4. We don't need backend or CMS access for the audit itself. If your site has specific authentication layers that affect crawling, we may ask for temporary crawl access, but that's discussed case by case.

Tools generate data. What you get from us is interpretation. We use similar tools in our process, but the value is in understanding which findings matter for your specific situation, what they mean in plain terms, and what a developer would need to do to address each one. A spreadsheet of 400 issues is not useful if you don't know which 12 to prioritize.

Typically one to two weeks from when we receive access and complete the intake questionnaire. Larger or more complex sites take longer. We give you a specific timeframe at the start of the engagement.

That's the entire purpose of what we do. The report is written assuming you understand your business and your website's purpose, but not that you know how to interpret server logs or write schema markup. Every technical term that appears is explained in context.

We deliver a structured document in PDF and a shareable online format. The developer brief section is also provided as a separate document formatted for easy handoff. We've found that having separate documents for the owner and the implementer prevents confusion.

Both. Every finding includes context about why it matters and what addressing it would involve. The prioritized fix list tells you which items to act on first. We don't find problems and leave you without direction.

No. Implementation is outside our scope. We prepare you to brief and manage whoever does implement the work, whether that's an in-house developer, a freelancer, or an agency. If you don't have a developer, we can suggest how to find one, but we don't provide that service ourselves.

The developer brief is written to stand on its own for a technical reader. If specific questions come up, there's a short follow-up window after delivery where we can clarify findings via email. Significant additional consulting is a separate engagement.

The report includes notes on how to verify each fix using GSC and other freely available tools. We walk through these verification steps during the delivery session so you know what to look for and on what timeline.

It depends on the scope of changes. For significant structural changes, a follow-up check makes sense. For a site with ongoing content production and regular updates, a periodic audit every several months is reasonable. We can discuss what makes sense for your situation.

Use the contact form or email us at [email protected]. Include a brief description of your site and what you're hoping to understand. We'll follow up to discuss scope and process before anything is formalized.

We send a short intake questionnaire at the start of the engagement. It covers your business context, recent site changes, specific concerns, your target audience, and the platforms and tools your site runs on. This shapes the audit so findings are relevant to your situation.

We work with sites on most major platforms including WordPress, Shopify, Webflow, Squarespace, and custom-built sites. Some platforms impose limitations on what can be changed technically, and we flag those limitations in the report where relevant.