Page count is an easy number to compare and a poor description of design effort. Five pages could mean one reusable template with copy swapped in, or a homepage, two distinct service layouts, a case study, and a custom contact flow. Both can be legitimate. You need to know what each page must do and how much unique work the quote includes.
Ask for a page-type list
Request a table with each page’s purpose, content source, layout type, and primary action. Mark which pages use a shared template and which get unique design or interaction work. A reusable system can keep the site consistent and reduce cost. It becomes a problem only when a page needs different proof, information structure, or action and the quote does not allow for it.
For example, two service pages may share typography and navigation yet require different questions, examples, and inquiry paths. A quote that includes “five pages” but excludes page-specific copy should say so. Otherwise the client may expect each service to be explained while the provider expects supplied text dropped into an existing component.
Check what the number excludes
Ask whether legal pages, thank-you pages, campaign landing pages, blog templates, case-study templates, location pages, and redirects count toward the total. Also ask whether the quote includes creating the content or only placing client-supplied material. Image selection, illustration, accessibility checks, and mobile layout can change effort even when the URL count stays fixed.
Check revision scope: does the provider review one visual direction for the whole site, or each unique page type? If an interior page is built after homepage approval, when can the buyer reject a poor fit without triggering new scope? Put those decisions in the milestone plan.
Compare the right unit of work
Instead of comparing only price per page, compare the number of unique layouts, content tasks, functional paths, and acceptance tests. A lower price can be a good fit for a small, simple offer. A higher price can be justified by integration, migration, content work, or distinct page types. Ask each provider to explain which of those is driving its quote.
At review time, check every page on mobile, verify approved copy and links, and test any form. Do not accept the homepage as a proxy for the rest. If five URLs share a template, still test each for missing content and broken actions.
ARCHV’s website service page says a proposal should specify pages and layouts. The website estimate is indicative until a person confirms the scope and final price. If you have two offers, the quote comparison can flag missing layout and content definitions. A contested review about the quality of secondary pages shows why the page-level promise needs to be explicit; it does not establish a general practice by any provider.
For the final decision, ask each agency to annotate the same proposed sitemap. That makes differences visible without forcing either one to match the other’s process. One may recommend combining pages because the offers overlap; another may recommend a dedicated page for a distinct audience. Evaluate the reasoning and the content plan, then choose the scope that serves your buyers.