A service page should help a homeowner, property manager, builder, or commercial buyer determine whether the contractor performs the relevant concrete work, where that work is available, what affects scope, and how to take the next step. Evaluate the rendered page and its real search data together instead of approving copy from a keyword document alone.
Dedicated service coverage. Evidence required: the current list of priority services, the live pages assigned to those services, and the concrete contractor SEO hub used to understand how those pages fit the wider topic.
Pass: each commercially important service has one useful destination when the business has enough distinct, supportable information to justify a separate page, and related pages have clearly different purposes.
Fail: a core service has no relevant destination, a thin page exists only to capture a variation, or multiple pages compete for the same customer need without a meaningful distinction. Severity: high when a core revenue service lacks a clear destination or when duplication makes the intended page ambiguous.
Owner: content lead with the business owner. Corrective action: create, merge, remove, or refocus pages around actual service scope, project suitability, limitations, proof, and contact paths. Validation: review the page map and internal links, then confirm every priority service has one intended destination that a reader can reach naturally.
Heading and query alignment. Evidence required: the rendered title, H1, H2, opening copy, internal anchor context, and Search Console query data for the page. Pass: headings and opening copy accurately describe the concrete service and genuine market served, and the language is understandable without mechanical repetition of city or service variants.
Fail: the title and primary content describe different services, headings imply a market the contractor does not genuinely serve, or repeated variants reduce clarity. Severity: medium when relevance is understandable but weakly expressed; high when the page communicates the wrong service or scope.
Owner: content editor. Corrective action: rewrite the page title, main heading, supporting heading, and opening copy so the primary service, audience, and next step are clear, then keep supporting copy natural rather than keyword-stuffed.
Validation: inspect the rendered page as a customer would and confirm the service can be identified without relying on metadata or a keyword report.
Cost guidance. Evidence required: current estimating inputs from the business, documented inclusions and exclusions, and an editorial review record showing what information is safe to publish. Pass: cost discussion explains the variables that change a concrete estimate and separates business-specific guidance from unsupported market claims.
Fail: the page presents an unsupported or outdated figure as verified market fact, hides major scope variables, or implies that a general example is a quote. A previously published example on this page used 8 to 15 per square foot for stamped concrete; because this JSON contains no supporting source URL for that range, it remains an editorial example that requires source reconciliation before publication.
Severity: high when unsupported pricing could materially mislead a prospective customer. Owner: business owner or estimator with the editor. Corrective action: replace unsupported ranges with current supportable guidance, or keep the discussion qualitative when reliable evidence is unavailable.
Validation: have the estimator confirm that the final wording matches how real projects are scoped and that any example is framed accurately.
Project image text. Evidence required: the original project image, its filename, current alt text, any caption, and the page context in which it appears. Pass: alternative text describes the useful visual content of the image, while nearby copy supplies only service and location context that is genuinely relevant.
Fail: text is generic, misleading, stuffed with terms, or claims a project, material, location, or result that cannot be confirmed from the asset and project record. For a legacy asset such as image1.jpg, rename it only when the publishing workflow can do so without breaking references; the required editorial fix is accurate descriptive text and trustworthy context.
Severity: medium, rising when a misleading image creates a false portfolio impression. Owner: content editor or site administrator. Corrective action: replace vague or promotional image text with concise descriptions grounded in the photograph and approved project details.
Validation: inspect the rendered page with the image unavailable or through an accessibility review and confirm the description still communicates the image's purpose without inventing context.
