Original framework
Audit pricing-factor matrix
The visible URL count is only one input. Scope should reflect how many distinct systems and decisions require investigation.
Why there is no responsible universal audit price
Two sites with the same number of URLs can require very different work. One may use a consistent server-rendered template; another may contain JavaScript rendering, faceted navigation, multiple markets, booking domains and recent migration risk.
A price without agreed scope can hide either shallow analysis or uncontrolled effort.
Website and platform complexity
The estimate should consider crawlable URL patterns, distinct templates, content-management rules, parameters, JavaScript dependence, third-party systems and the effort required to reproduce important behavior.
Business and search complexity
Multiple countries, languages, genuine locations, service areas, regulated claims or separate brands increase the decisions that must be evaluated. Priority journeys and commercial pages should be identified before coverage is agreed.
Available evidence
Search Console, analytics, release history and server logs can strengthen diagnosis but also require access preparation and analysis. A traffic-loss or migration investigation usually needs a different evidence set from a routine baseline audit.
Deliverable depth and collaboration
A concise issue register costs less to produce than detailed developer tickets, acceptance criteria, stakeholder workshops, redirect maps, staging reviews and post-release QA. The quote should state which outputs and communication windows are included.
Example scope models
A focused investigation addresses one defined problem or template. A baseline audit reviews the important technical systems across the site. A migration or implementation engagement adds release planning, validation and monitoring.
These are scope models, not fixed price bands. Brainideas Digital confirms a proposal only after the website, evidence and required outcome are understood.
What a useful proposal should state
Look for the audit objective, included systems, sample or crawl limits, access assumptions, deliverables, meetings, timeline factors, implementation responsibility, QA coverage, exclusions and payment terms.
Do not evaluate an audit only by the number of checks or exported rows. The useful outcome is a validated, prioritized decision record.