- 01
Inventory actual destinations
List the canonical public URLs for important services, locations, team information, and appointments. Check their current response and redirect destinations. A URL saved in a spreadsheet is not evidence that the page is still live.
- 02
Check discoverability
Make important pages reachable through relevant internal links. Use descriptive labels that help a visitor choose a destination. Avoid leaving a useful page isolated while adding another nearly identical one to chase a different phrase.
- 03
Inspect the rendered page
Confirm that the main information is present, readable, and not hidden behind a broken script. Check titles, headings, images, and mobile behavior. Structured data should describe what the reader can actually see and verify.
- 04
Verify after changes
Clear applicable caches for the changed site and inspect the public page without an administrator login. Recheck important internal links and any intentional redirects. Record failures as open work rather than calling a deployment successful because files were uploaded.
A planning exercise, not a client result
Put the idea to work
Planning exercise: a useful service page exists but the menu points to an old address that returns an error. Repair the destination and relevant links, then verify the public journey. Publishing another article would not fix the original technical obstacle.
What to watch for
- Checking files instead of the public page
- Unnecessary duplicate destinations
- Structured data that exceeds visible evidence