Finding stale contact details inside structured data
To find stale contact details in structured data, compare each published contact value with an approved current source and the visible page. Search for the old value across publishing inputs so a corrected page does not inherit it again.
Establish the approved contact record
Ask the responsible organization which contact details are public and current. Record the purpose of each number or address, because a general enquiry contact and a department contact may both be legitimate. Avoid treating the most frequently repeated value as authoritative. If the business has not confirmed which version is correct, mark the fact unresolved rather than selecting the newest-looking page.
Compare the full contact representation
Inspect the structured-data blocks that describe the business on the affected page. Record every relevant contact value and the entity it belongs to. Read the visible contact section at the same time. Google requires accurate structured data that reflects visible content. A current visible phone number does not excuse a stale number in markup, and a valid block does not verify either number.
- Approved value, purpose, and confirming source.
- Visible value and page location.
- Structured value and associated entity.
- Old value and publishing source requiring correction.
Track the old value upstream
Look for the obsolete detail in the templates, content records, or configuration that publish the reviewed pages. Keep the search focused on that exact value and known variants. Distinguish live content from historical records before editing; an archived change log may properly preserve the old contact. Correct the active source and note which pages depend on it. Do not rewrite unrelated business details during a narrow contact correction.
Verify the intended public result
Reopen the affected public pages after the update and compare visible and structured values again. Record which pages were checked and which remain outside the sample. If different contacts intentionally remain, document their purposes so the next audit does not undo the decision. The result is verified consistency, not a promise of a search feature. Continue related identity checks through /website-analyzer/.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Should all telephone numbers on the site match?
Not necessarily. Different verified purposes can justify different numbers. The important comparison is between the intended contact, its visible description, and its structured representation.
Can I delete every occurrence of an old number?
First separate active publishing inputs from historical records. Correct current public claims while preserving useful dated evidence where appropriate.