October 28, 2026: Review reminders and continued recipe access

Review dates flag maintenance work

Review dates are maintenance reminders. Published guidance remains available after a deadline; new or changed guidance needs exact-content review before publication, and known unsafe or incorrect guidance can be explicitly withdrawn. Check current primary sources before acting on dated or sensitive claims.

The same knowledge edition stays in use

The published knowledge edition is unchanged: claude-discoverability-0.9.0-9d3ebe8b5bc5. Recipe and source dates retain their recorded values. Retained published editions remain readable by exact pin after their review dates; explicit withdrawals and publication controls still apply.

Website guidance extends beyond migration

The 217 entries include practical methods, workflows, verification checks, deeper chapters, references and worked cases, with supporting claims and competencies. Coverage includes migration and traffic preservation, search, local profiles, DNS and email, measurement, content, website imagery, social visibility, market research, accessibility, privacy and terms review. This is not a count of 217 separate jobs.

Service checks have a defined scope

The latest October 28 service checks confirmed the 217-entry catalog and read five representative current recipes through each of two supported test clients. An earlier October 28 sweep read all 217 entries through both clients. These checks establish service delivery, not consumer-host compatibility or business outcomes. A retained recipe whose review date had passed also returned its original guidance through both supported test clients.

Source and editorial reviews retain their own dates

The earlier October 28 knowledge maintenance checked 25 source records against primary documentation and gave 25 affected entries exact-content same-author AI review, not independent review. The later review-reminder change did not renew those dates or rewrite the recipes. Source checks, editorial review, software validation and testing in an actual AI host are separate records.

Your AI applies the guidance with your authority

The service supplies read-only guidance through search_guidance and get_guidance. Your AI keeps private evidence and work state in your workspace and uses its own permitted tools. This release adds no website execution, account access, customer-project storage or scheduled monitoring. Rankings, AI recommendations, legal compliance and additional enquiries are not established by these checks.

Edition and verification record

The public service requires no FidelicAI sign-in. Your AI host may have its own account, plan or organization requirements. Directory listing approval is separate and is not established by a working connection.

Traffic preservation remains part of the cookbook

The October 16 release strengthened preservation of useful pages, addresses, content and customer paths during a move or update. Those methods remain part of the cookbook. A working redirect is a technical check; retained traffic and enquiries need later observations.

Sources and next steps