Service scope
Technical SEO
Understand what prevents your important pages from being discovered, crawled, and interpreted. Start with evidence, agree which fixes belong in scope, and verify the implementation before judging search performance.
For a business website or online store with indexing inconsistencies, duplicate URLs, a recent migration, weak page structure, or an unclear technical backlog. It is also a useful starting point before commissioning more content.
Discuss Technical SEO scopeDeliverables
- A prioritised issue register covering affected URLs, evidence, likely impact, recommended action, and who needs to implement each fix.
- Crawl and indexing checks for robots rules, sitemap entries, response codes, redirect chains, canonical tags, internal links, and key page templates.
- An entity and structured-data review: relevant types, stable identifiers, connected references, and consistency with visible page content.
- Performance and accessibility observations for representative templates, separating lab measurements from available field data for LCP, CLS, and INP.
- For implementation engagements, agreed code or configuration changes with before-and-after checks, release notes, and a handover checklist.
What you need to provide
Send the website URL, business priorities, target regions, and any migration history. Read-only Search Console and analytics access help distinguish technical symptoms from traffic changes. Implementation also requires the appropriate CMS or repository access, a backup or rollback route, and a person who can approve releases. Invite access using roles; do not send passwords through the contact form.
Timelines and dependencies
An initial reply is targeted within 24 hours. A standard free audit summary is targeted within 48 hours after website details and required access arrive; a full paid audit is a separate scope. Its milestones and implementation dates are confirmed after reviewing site size, platform constraints, approvals, and developer availability. Search outcomes have no fixed delivery date.
Pricing approach
Quotes reflect the number of URLs and templates, platform complexity, access limitations, migration work, and whether remediation is included. Audit-only, implementation, and ongoing monitoring can be scoped separately. The proposal identifies deliverables, currency, review rounds, payment stages, and any approved third-party costs before work starts.
Ownership and handover
Keep the domain, hosting, analytics, and Search Console properties under your business’s control. Handover includes the agreed findings, change notes, and custom files or repository changes. The proposal records any third-party licences and the terms for custom work; recurring monitoring is separate from access to your own accounts.
Reporting and evidence
The audit report links each finding to evidence and an owner. Implementation reporting records changes, checks, unresolved dependencies, and release dates. For agreed ongoing work, monthly reporting separates indexing status, impressions, clicks, traffic, and tracked conversions; comparisons note the date range, seasonality, and data gaps.
Limitations and exclusions
A technically accessible page can still be excluded from search. Rankings, traffic, rich results, and revenue gains are not guaranteed. Crawl samples may miss pages; unavailable logs or field data are documented. Content production, paid links, server administration, legal review, and unlimited development are outside scope unless explicitly included.
How the work proceeds
Baseline and boundaries
Agree the important URLs, site size, template sample, current tracking, and whether the engagement covers recommendations or implementation. Record what cannot be inspected.
Evidence and priorities
Review crawl paths, indexing signals, schema, and template performance. Separate urgent access problems from enhancements, and identify dependencies on developers, hosting, or content approval.
Implementation and verification
Apply only approved changes, verify the affected templates, and document redirects and rollback steps. Resolve acceptance issues against the agreed scope before handover.
Monitoring
If monitoring is commissioned, compare subsequent Search Console and analytics data with the baseline. Recrawling and ranking changes happen on the search engine’s timetable, not at the moment a patch is released.
Frequently asked questions
What will I receive?
A prioritised issue register covering affected URLs, evidence, likely impact, recommended action, and who needs to implement each fix. Crawl and indexing checks for robots rules, sitemap entries, response codes, redirect chains, canonical tags, internal links, and key page templates. An entity and structured-data review: relevant types, stable identifiers, connected references, and consistency with visible page content. Performance and accessibility observations for representative templates, separating lab measurements from available field data for LCP, CLS, and INP. For implementation engagements, agreed code or configuration changes with before-and-after checks, release notes, and a handover checklist.
What do you need before starting?
Send the website URL, business priorities, target regions, and any migration history. Read-only Search Console and analytics access help distinguish technical symptoms from traffic changes. Implementation also requires the appropriate CMS or repository access, a backup or rollback route, and a person who can approve releases. Invite access using roles; do not send passwords through the contact form.
When will I receive the work?
An initial reply is targeted within 24 hours. A standard free audit summary is targeted within 48 hours after website details and required access arrive; a full paid audit is a separate scope. Its milestones and implementation dates are confirmed after reviewing site size, platform constraints, approvals, and developer availability. Search outcomes have no fixed delivery date.
How is the engagement priced?
Quotes reflect the number of URLs and templates, platform complexity, access limitations, migration work, and whether remediation is included. Audit-only, implementation, and ongoing monitoring can be scoped separately. The proposal identifies deliverables, currency, review rounds, payment stages, and any approved third-party costs before work starts.
Who owns the accounts and receives the files?
Keep the domain, hosting, analytics, and Search Console properties under your business’s control. Handover includes the agreed findings, change notes, and custom files or repository changes. The proposal records any third-party licences and the terms for custom work; recurring monitoring is separate from access to your own accounts.
What evidence and reporting will I receive?
The audit report links each finding to evidence and an owner. Implementation reporting records changes, checks, unresolved dependencies, and release dates. For agreed ongoing work, monthly reporting separates indexing status, impressions, clicks, traffic, and tracked conversions; comparisons note the date range, seasonality, and data gaps.
What is outside scope or cannot be guaranteed?
A technically accessible page can still be excluded from search. Rankings, traffic, rich results, and revenue gains are not guaranteed. Crawl samples may miss pages; unavailable logs or field data are documented. Content production, paid links, server administration, legal review, and unlimited development are outside scope unless explicitly included.
Will you implement the fixes or only deliver an audit?
Either can be scoped. An audit-only engagement provides evidence and a prioritised backlog. Implementation requires a separate approved list of changes, suitable access, testing and release responsibility. The proposal states which fixes are included and which need your developer or hosting provider.
Start with the scope
Send your website or asset URLs, priorities, and relevant constraints. Please do not send passwords or sensitive documents through the enquiry form. The next step is to confirm what can be reviewed, what needs access, and what belongs in a written proposal.
Platform reference: Google Search Essentials. Platform requirements may change; eligibility and available permissions are checked during scoping.