This check is for small-business owners, in-house marketing managers, solo founders, and agency account managers who already own an older site and need to decide which service pages to keep, rewrite, redirect, or remove before a redesign, SEO push, or ad spend. The risk is not just stale wording: an old page can still promise a discontinued offer, show the wrong proof, track the wrong lead action, or send buyers into a sales process the team no longer uses.
An older business website often describes a past version of the company. Services change, pricing changes, target buyers shift, proof gets old, and sales conversations move on. A service-page audit compares the public site against what the business actually sells now, then turns each mismatch into a clear action: keep, rewrite, redirect, or remove.
Short answer: keep the page when the offer, buyer, proof, CTA, and sales handoff still match the current service. Rewrite it when the service still exists but the message, examples, or process are wrong. Redirect it when the service is permanently retired and a close replacement exists. Remove it from the normal customer path when there is no useful replacement, no buyer value, and no reason to keep it discoverable.
Compare Pages to Today’s Offers
Start with an offer inventory, not a design review. Put the homepage, main navigation, service pages, pricing sections, FAQs, contact forms, and calls to action beside the current proposal template, sales deck, intake form, and fulfillment checklist. Google Search Essentials and Google’s title guidance both point back to the same practical idea: use clear words people recognize, keep important links crawlable, and make the page title match the page content.[1][2] The service name in the H1, nav label, title tag, internal links, and CTA should all point to the same current offer.
For each high-intent URL, record the offer name, buyer, service area, price or scope language, CTA, proof, and next step. If a page cannot be tied to a current offer in the sales process, it should not sit unchanged just because it still exists in WordPress. A stale page for “one-time SEO tune-up,” for example, should be rewritten if the business now sells ongoing website maintenance, or permanently redirected if the service is gone and a closer live service exists.
Also check the markup, but do not overstate it. Schema.org Service markup can help keep page data consistent with the visible offer, and Google’s structured data guidelines say structured data should be visible to readers, representative of the main page content, and up to date.[3][4] Treat schema as a consistency check, not as the main reason to keep or rewrite a page. Service is not a Google rich-result type by itself, so the visible promise still matters more than the markup.
- Homepage and navigation: if the menu still says “Web Design” but the sales team now sells “Website Maintenance,” update the label, destination URL, and homepage CTA together so visitors do not bounce between two offers.
- Service page: if the page sells a discontinued audit, replace the offer details with the current package or redirect it to the closest active service using a permanent server-side redirect when the move is permanent; Google’s redirect documentation identifies 301 and 308 as permanent redirects.[5]
- Pricing and FAQ: if the FAQ promises a fixed turnaround, unlimited revisions, or support channel that operations no longer provides, rewrite it before changing ads or title tags.
- CTA and forms: if the page asks for the wrong qualification details, update the form fields and the main lead action so lead quality can be judged against the current service, not the old one.
Mini-workflow for a retired service page:
- Crawl the site with a crawler such as Screaming Frog SEO Spider, and export indexable service URLs, status codes, titles, H1s, canonicals, and inlinks.[6]
- Choose one candidate URL and compare the public promise against the current proposal, sales script, and fulfillment checklist.
- If the service still exists but the buyer, scope, or proof has changed, rewrite the page in place and keep the URL if it still matches search intent.
- If the service is permanently retired and a close replacement exists, redirect the old URL to the replacement and update internal links so visitors do not pass through the redirect.
- If there is no close replacement, remove the page from navigation and decide whether it should return a helpful gone/removed state, stay archived for a narrow reason, or be excluded from search.
- If the page stays live, update visible copy, Service schema, CTA text, and the lead event before judging performance.
Check the Buyer and Proof
The website may still show old industries, small early clients, anonymous testimonials, or examples that do not match the desired customer. Proof should support the current direction of the business. Google’s guidance on helpful, reliable, people-first content asks whether content shows clear sourcing, evidence of expertise, and enough information for a reader to achieve their goal.[7] A service page with thin claims and dated proof fails that test even if the keywords still look right. Content that may appear in AI features also needs the visible page to answer the buyer’s real question, not just repeat a service keyword.[8]
Use buyer evidence from Search Console queries, GA4 landing pages, CRM notes, call recordings, and closed-won proposals. If a page attracts founders looking for a cheap setup but the business now sells monthly support to established local service firms, the mismatch is not a copy polish issue. It is a positioning issue that will keep producing poor-fit inquiries until the page names the right buyer and filters the wrong one out.
In audits, two failure patterns show up often. One is the retired starter offer that still ranks and still collects form fills, even though every qualified buyer is now moved into a retainer. The fix is usually not a prettier page; it is a rewrite that explains the current recurring service, plus redirects from any old package URLs that no longer represent a real buying path. The second is the old proof problem: the page says the agency serves established local service firms, but the screenshots and testimonials all come from early startup work. That page needs new examples before it needs new adjectives.
- Remove discontinued offers: if “logo design” is no longer sold on its own, stop presenting it as a standalone service and point visitors to the current brand or website package only if that is what sales actually offers.
- Update examples and case studies: if the page sells maintenance, use proof about uptime, fixes, support response, or recurring work, not only a launch announcement from a one-time build.
- Rewrite pages that speak to the wrong buyer: if the page says “for startups” but the intake form and sales calls now qualify established businesses, change the headline, objections, proof, and CTA to match that buyer.
- Cut vague proof: replace “trusted by businesses of all sizes” with specific client types, project types, service areas, or outcomes that can be verified internally before publishing.
Score Each Service Page
A simple score keeps the audit from turning into a subjective copy review. Give each page 0, 1, or 2 points in five areas: current offer, right buyer, current proof, accurate process, and useful conversion path. A 2 means the page matches what the business sells now. A 1 means it is partly right but needs a visible fix. A 0 means the page actively misleads buyers or sales.
| Score | Meaning | Usual action |
|---|---|---|
| 8-10 | The page mostly matches the current service and sales path | Keep it, then make small copy, proof, or CTA updates |
| 5-7 | The service still exists, but the buyer, proof, scope, or process is off | Rewrite in place and update internal links if labels changed |
| 1-4 | The page describes a mostly retired or heavily changed offer | Redirect to a close replacement, or rewrite only if the URL still fits intent |
| 0 | The page has no current offer, no useful replacement, and no buyer value | Remove it from the customer path and avoid redirecting to an unrelated page |
Check the Sales Process
Timelines, deliverables, support levels, contact paths, onboarding steps, and qualification questions should match current operations. A visitor should not read one process on the website and hear another on the sales call. The cleanest audit question is simple: can a salesperson use this page as-is during a live conversation without correcting it?
Measurement has to support that decision, but it should not take over the article. GA4 recommended events include generate_lead when a user submits a form or request for information, and Google Tag Manager uses tags, triggers, and variables.[9][10] For this audit, the practical check is narrow: after a rewrite or redirect, confirm that the main form submit, booking click, phone click, or account signup still fires the intended lead event.
Accessibility and performance belong in the same narrow lane. If a quote form has no label, the button contrast is weak, a booking embed shifts the page, or the main CTA is slow to respond, the page is not ready to judge fairly. WCAG 2.2, Core Web Vitals, INP, and PageSpeed Insights are useful references for those checks, but they do not decide whether the offer matches the business.[11][12][13][14]
Prioritize High-Intent Pages
Start with pages closest to a buying decision. Service pages, contact pages, pricing pages, comparison pages, location pages, and proposal-linked URLs matter most because they shape buyer expectations before a call. A blog post can be stale and still educate. A stale service page can create a bad lead, a bad quote, or a support dispute.
| Page type | Match check | Fail signal | Action |
|---|---|---|---|
| Homepage hero | Current primary offer, buyer, and CTA | The hero promotes a service the team no longer sells | Rewrite hero, nav label, and CTA together |
| Service page | Offer name, scope, area served, proof, and markup | Visible copy and Service schema describe different offers | Update copy and markup so both describe the same service |
| Pricing or package page | Current price logic, inclusions, exclusions, and sales handoff | Visitors expect a fixed package that sales no longer quotes | Rewrite pricing language or replace with a qualification CTA |
| Contact or quote page | Fields, labels, routing, and lead event | The form qualifies for an old service or fires the wrong event | Update fields, labels, trigger, and event mapping |
| Comparison page | Current alternatives and decision criteria | The page compares against a service category the buyer no longer considers | Rewrite around the current sales objection or consolidate |
Optional second pass: before assigning a full rewrite, enter one candidate URL on Website Advisor and use the audit as a check against the manual inventory. Run it while the page is still being triaged, not after the rewrite is already approved.
Use this decision rule tomorrow: keep the page when the public promise, sales process, proof, tracking, accessibility, and performance all support the same current service; rewrite it when the offer still exists and the audience, proof, or process is wrong; redirect it when the offer is permanently retired and a close replacement exists; remove it from the customer path when it no longer helps a buyer and has no close replacement.
FAQ
How often should an older business site run a service-page audit?
Run it after any offer, pricing, service area, fulfillment, or sales qualification change. Also run it before a redesign, SEO campaign, ad campaign, or major content refresh, because those projects can send more traffic into pages that already say the wrong thing.
Should old service pages be deleted or redirected?
Not by default. If the service still exists, rewrite the page. If the service is permanently retired and a close replacement exists, use a permanent redirect and update internal links. If there is no close replacement, do not redirect visitors to an unrelated page just to preserve traffic.
What if analytics is missing or messy?
Use a manual inventory first: current proposals, sales notes, form submissions, and pages linked from the main nav. Then fix measurement so the next audit has lead-quality evidence, not guesses.
Do Core Web Vitals decide whether the service page matches the business?
No. Core Web Vitals measure loading, interactivity, and visual stability. A page can pass those thresholds and still sell the wrong service. Treat performance as a readiness check alongside offer accuracy, proof, accessibility, and conversion tracking.
Sources
Last reviewed: 2026-04-23 for the Google Search Central, web.dev, W3C WCAG, GA4, and Google Tag Manager references below.
- Google Search Essentials: https://developers.google.com/search/docs/essentials – crawlable links and useful page basics.
- Google title links guidance: https://developers.google.com/search/docs/advanced/appearance/good-titles-snippets – title links and snippet quality.
- Schema.org Service: https://schema.org/Service – Service markup properties.
- Google structured data guidelines: https://developers.google.com/search/docs/appearance/structured-data/sd-policies – structured data quality and content alignment.
- Google redirects documentation: https://developers.google.com/search/docs/crawling-indexing/301-redirects – permanent redirect handling.
- Screaming Frog SEO Spider user guide: https://www.screamingfrog.co.uk/seo-spider/user-guide/ – crawling exports for URL inventories.
- Google people-first content guidance: https://developers.google.com/search/docs/fundamentals/creating-helpful-content – expertise, evidence, and reader usefulness.
- Google AI features in Search: https://developers.google.com/search/docs/appearance/ai-features – content eligibility and search feature context.
- GA4 recommended events: https://support.google.com/analytics/answer/9267735 – lead-generation event names.
- Google Tag Manager basics: https://support.google.com/tagmanager/answer/6102821 – tags, triggers, and variables.
- WCAG 2.2: https://www.w3.org/TR/WCAG22/ – accessibility conformance and success criteria.
- web.dev Core Web Vitals: https://web.dev/articles/vitals – loading, interaction, and layout stability thresholds.
- Google Search Central INP update: https://developers.google.com/search/blog/2023/05/introducing-inp – INP replacing FID as a Core Web Vital.
- PageSpeed Insights documentation: https://developers.google.com/speed/docs/insights/v5/about – field data and lab diagnostics.