Q3 Brand Profile Freshness: What to Re-Verify Before Fall AI Overview Crawls

Summer launches leave winter citations

Q3 is when brands ship a renamed SKU, move HQ copy, or retire a product — and leave BrandSource, homepage JSON-LD, and Wikipedia/Wikidata on June facts. Retrieval systems prefer the dated page they already indexed. If last-verified did not move, you are still the June entity.

This is an operations checklist, not a ranking promise.

Re-verify these six fields this week

• Canonical name — legal vs product vs campaign name after a summer rebrand
• Product lines — drop SKUs you sunset; add named lines you actually sell in September
• Headquarters — marketing “global” vs the city in Organization schema
• Official website — apex vs www vs a campaign subdomain that 302s
• sameAs — dead LinkedIn, merged Wikipedia, or a lookalike brand
• last-verified — only bump after the five fields above match live pages

If a field cannot be traced to a public URL, cut it. Invented freshness is worse than an old accurate date.

Citation surfaces to keep in parity

- BrandSource profile: `https://brandsource.ai/brands/{slug}` - JSON-LD: `https://brandsource.ai/api/brands/{slug}/json-ld` - Your homepage Organization schema (same name, HQ, URL) - Crawler-oriented host: ai.brandsource.ai for discovery, not as a second identity

Do not treat social bios or “top tools” roundups as the source of founding year or product scope.

FAQ

Is bumping last-verified without edits useful? No. Freshness without a changed fact trains systems to ignore your date.

We launched in August — do we need a new BrandSource page? Usually no. Update product lines and evidence on the existing slug. A second profile splits the entity.

How do I edit? Claim your profile, align fields to live docs, then re-verify. Browse canonical records at brandsource.ai/brands.

Next step

Pick one brand you own. Diff BrandSource against the homepage schema and the top product docs URL. Fix the first mismatch before touching anything else.