Feature crawler coverage, speed guarantees and AEO in the listing - #16
Merged
Conversation
Three claims in the new copy outran the implementation. Codex caught all three; each is a case of documentation describing the design's intent rather than its behaviour. "Cannot slow your site down" was false on the crawler path. The cache-only guarantee belongs to the render that serves a person; Citecue_Proxy::decide() deliberately makes a synchronous lookup for a recognised crawler, because only a bot is waiting there, and can spend up to the three-second serve timeout before the circuit breaker trips. The bullet is now "Never makes a visitor wait", which is the guarantee that actually holds, and it states the crawler exception and its bounds rather than hiding it. "Never to Google" was wrong in the one place it mattered. GoogleOther is in the bundled registry and is advertised two lines above and on the banner, so the optimized page IS served to a Google crawler. The answer now separates the two: GoogleOther, which Google uses for its AI products, is served; Googlebot, which crawls for Search, is not in the registry and gets the ordinary page. And the cloaking answer omitted the only visible thing the question is about. It said a reader sees the page plus additive metadata, which contradicted both the feature list and the neighbouring FAQ answer this same branch had already corrected for 1.2.0. Page enhancements are now named there, alongside the point that matters: a reader and Googlebot receive identical bytes. Verified rather than assumed: Googlebot is absent from bundled_tokens(), which holds exactly the 18 entries the description claims, and the per-minute lookup budget and three-second timeout are both real. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds three things the readme/banner under-sold, corrects one FAQ answer that 1.2.0's page enhancements make false, and puts AEO in the hero. Stacked on and now clean against #15 (merged).
AEO · AI CRAWLERS · SEO METADATA), the short description, and the Description's opening sentence, matching how citecue2's own content (the AEO pillar post, GEO/AEO/SEO framing) already uses the term.Caught by Codex review, fixed here
The first draft overclaimed in three places; codex:review caught all three, verified against source before fixing:
Citecue_Proxy::decide()makes a synchronous lookup for a recognised crawler (only a bot is waiting, so this is deliberate) and can spend up to the 3-second serve timeout before the circuit breaker trips. The cache-only guarantee is real for the visitor render path only — the bullet and FAQ answer now say so explicitly, including the bound (3s timeout, per-minute budget, circuit breaker).GoogleOther— which Google uses for its AI products — is in the bundled registry and is served the optimized page; it's advertised two lines above this same answer.Googlebot(Search) is not in the registry. The FAQ now names both and says which is which.Verified against
includes/class-citecue-crawlers.phpbefore writing the correction:Googlebotis absent frombundled_tokens(), which holds exactly the 18 entries the copy claims.Verification
phpcsandcomposer lintcleanassets-src/build-assets.sh, dimensions assertedNote for whoever pushes to SVN next
This PR's readme changes describe 1.2.0 (page enhancements, 18-crawler registry, AEO framing) and must not be copied onto the currently-published 1.1.2 listing — none of that is true of the code that version ships. The one exception already pushed separately:
Tested up to: 7.1, which is true of every published version and was pushed to SVN readme-only, ahead of this merging.🤖 Generated with Claude Code