Core search platform
✅
Independent search index online — GoGuides has its own crawl, index, and search pipeline serving real results outside the major ad-driven search platforms.
✅
AI quality scoring is active — crawled pages receive a 0–100 AI Rank that helps separate stronger, cleaner, more useful pages from low-quality or noisy results.
✅
Search combines relevance with GoGuides quality and record-state signals — public search can use indexed relevance together with supported AI Rank, freshness, eligibility, and observed-state context rather than relying on keyword matching alone.
✅
Site-specific search and safety filtering are active — dedicated site-query handling and public-result filtering help keep ineligible, irrelevant, or restricted results out of ordinary user-facing search paths.
✅
Crawler robots.txt compliance is active — GoGuides now checks publisher crawl rules before fetching pages, and robots-disallowed URLs are not fetched, scored, or saved by the crawler.
✅
GoGuidesCrawler transparency is live — the crawler user-agent points to
/crawler, giving site owners a clear explanation page, robots.txt guidance, domain lookup path, and Live Index submission path.
✅
Smarter title and description extraction is live — the crawler now uses cleaner title fallbacks and rejects weak, spammy, or keyword-stuffed meta descriptions before storing search-facing text.
✅
Public quality eligibility filtering is active — parked domains, domain-for-sale pages, recovered demo sites, stale make-money pages, and group-link farms can be withheld or demoted from public search presentation under GoGuides quality and eligibility rules.
✅
Known low-quality site results are no longer presented as clean listings — site-specific searches now respect the public AI Rank floor and explain when a known domain has no eligible clean public listing.
Signals & request observation
✅
Search interaction and feedback signals are supported — supported search surfaces can record impressions and user interactions such as clicks, saves, reports, or revisits as product feedback signals.
✅
Public signal feed is live — eligible domains can appear in a machine-readable discovery feed that exposes selected GoGuides record-state signals to humans and automated consumers.
✅
Public AI Bot Radar is live — anyone can check whether qualifying AI and search activity has recently been observed for a domain, while detailed identities, timelines, request counts, endpoint activity, and return patterns remain part of the activated experience.
✅
Detailed AI Bot Radar is live in the user panel — included domains can receive deeper daily and historical views of identified systems, request counts, endpoints, timing, return patterns, and monitoring history.
✅
Bot activity context is connected to public GoGuides record surfaces — qualifying observed request activity can be inspected alongside supported profiles, history, verification context, machine-readable records, and related public resources without claiming access to a website owner’s private server logs.
✅
Observation timeline signals are visible — supported reports can show first seen, last observed, observation count, days observed, record age, stability windows, current state timing, and rank/algo state changes.
✅
Record-state fingerprints are live — GoGuides can expose SHA-256 fingerprints for defined stored record state so machine consumers can identify and compare represented state without confusing the fingerprint with ownership verification.
Webmaster & site-owner tools
✅
Live Index submission flow is live — authorized site owners and agencies can submit a domain through the public eligibility and inclusion workflow while GoGuides evaluation remains independent of payment.
✅
Paid inclusion does not buy a favorable evaluation — Live Index inclusion does not purchase a higher AI Rank, better grade, favorable policy outcome, or search ranking.
✅
The AI visibility utility network is live — GoGuides now answers high-intent webmaster questions about AI crawler visits, ChatGPT visibility, possible AI use, robots.txt, crawler observation, and recent activity through the public AI Bot Radar.
✅
Tool-backed reports are live — those pages let a site owner enter a domain and inspect available GoGuides observations, provenance, verification context, machine-readable state, and supported automated-request evidence.
✅
Observation and ownership states are separated — reports distinguish independently observed web state from owner-connected or ownership-verified status, and absence of a GoGuides record is not presented as proof that a domain is untrusted.
✅
Observation, verification, and Live Index states are separated — GoGuides distinguishes independently observed domains, ownership context, and approved paid Live Index inclusion rather than treating them as the same state.
✅
Public profile-link button workflow is live — supported site-owner surfaces can link visitors back to the domain’s GoGuides profile and public history context without treating the button itself as a certificate of truth.
✅
Public-to-detailed Bot Radar path is live — visitors can begin with a public lookup, inspect available domain and history records, and eligible included domains can access identified systems, detailed counts, endpoints, timelines, and return patterns.
✅
Primary Topic selection is live — supported included domains can declare one high-level topic used to organize public GoGuides metadata.
✅
Site Keywords selection is live — activated domains can choose up to three crawler-detected keywords without free-form keyword stuffing or paid-link confusion.
Deterministic record-state visualization
✅
Deterministic favicon record-state visualization is live — GoGuides generates repeatable visual state from the authoritative resolved record inputs supported by the renderer; it is a record-state visualization, not a certificate or universal trust verdict.
✅
Public record surfaces are connected — favicon record-state visualization is linked with supported profile, verification, and history context so the visual state can be inspected against the underlying public record.
✅
Visual record state resolves from supported authoritative inputs — the renderer can reflect supported rank, observation-time, verification, and public-state inputs while keeping those inputs distinct from the image itself.
Evidence & provenance
✅
Public Trust Record is live — observed domains can expose a public measurement record showing rank, grade, crawl timing, verification state, timeline data, and trust-history context.
✅
Public Trust Profile is live — eligible domains can expose a human-readable public profile showing current GoGuides record context, timeline information, public status, and ownership-verification context as separate concepts.
✅
Evaluate v3.2 is machine-readable — domain and supported exact-URL evaluation resolve through authoritative scope-specific record paths and return structured GoGuides evidence, interpretation, eligibility, freshness, verification, and related-resource context.
✅
Web State V3 endpoint is live — /state/{domain} provides a JSON-first current-state record built from stored GoGuides observations, including text similarity, structured-data state, response-header fingerprints, content size, internal and external link counts, outbound-link fingerprints, AI policy state, and observation metadata.
✅
Evaluate now discovers Web State — machine-readable evaluation records expose state_url, creating a deliberate path from GoGuides trust and eligibility decisions into deeper current website-state intelligence.
✅
Web State activity is integrated with AI Bot Radar — requests to the State endpoint are recorded as a first-class machine surface alongside other GoGuides trust and intelligence endpoints, supporting lifetime and rolling activity observation.
✅
Observation timeline and record fingerprinting are live — first seen, last observed, observation count, days observed, stability window, state changes, and SHA-256 record-state fingerprints expose measurable longitudinal context.
✅
Domain Provenance Records are live — GoGuides history pages preserve independently observed website states over time, including requested and final URLs, HTTP response state, redirects, canonical identity, content fingerprints, robots.txt evidence, DNS and nameserver observations, HTTPS/TLS certificate identity, and observation history.
✅
Historical website-state change detection is live — changed public states can create new provenance records while repeated unchanged observations strengthen the historical record, making meaningful changes to content, canonical identity, network state, TLS information, robots behavior, and related public evidence easier to identify over time.
✅
Domain provenance is machine-readable — structured provenance observations can be exposed alongside public trust information so developers and automated systems can inspect historical website state and supporting evidence without relying only on a rendered webpage.
✅
Change Intelligence V1 is live —
/changes/{domain} compares consecutive Web State V3 observations of the same requested URL and returns machine-readable change classifications including
content_changed,
structured_data_changed,
outbound_links_changed,
ai_policy_changed,
http_status_changed,
refresh_recommended, and
refresh_reason. It operates from stored GoGuides observations; freshness maintenance is asynchronous.
Machine discovery & contracts
✅
Public AI Discovery Feed is live —
AI Discovery Feed gives AI systems, crawlers, search engines, developers, and automated agents a plain-HTML discovery path into gate-approved Trust Records, Trust Profiles, history pages, and evaluation JSON.
✅
Machine-readable integration documentation is live — the
Machine-Readable Integration Guide demonstrates endpoint discovery, domain trust inspection, Verified Text retrieval, canonical record use, and independent SHA-256 verification without implying endorsement by outside AI or search companies.
✅
Canonical OpenAPI 3.1 machine contract is live —
/docs/openapi.yaml formally documents the public Evaluate, Web State, Change Intelligence, Signal, Verified Text, AI URL Request, and URL Request Status interfaces so developers and automated systems do not have to infer endpoint behavior from examples alone.
✅
AI URL Request is live —
POST /request-url lets a machine client request intelligence for one public URL, receive existing supported intelligence when available, and follow the documented request lifecycle without being able to create authoritative GoGuides state directly.
✅
Request intent and authoritative observation are separated — submitting a URL records request intent; authoritative GoGuides state still comes from GoGuides’ independent observation and resolver paths rather than from caller-supplied assertions.
✅
Web Bot Auth identity evidence is supported — supported signed requests can be checked using RFC 9421 HTTP Message Signatures and the documented Web Bot Auth identity mechanism, while claimed User-Agent identity remains distinct from cryptographically supported identity evidence.
✅
Web State V3 has canonical machine-readable semantics —
/docs/web-state.json defines the nine Web State fields, AI-policy and schema-type bitmasks, decoded companions, omission semantics, zero-value semantics, unknown-bit handling, and forward-compatibility rules.
✅
Machine discovery now links directly into the formal contracts —
/machine-use.json advertises both the OpenAPI definition and Web State semantics, establishing a deterministic machine path from service discovery to endpoint contract to field interpretation.
✅
Public Data License is live — GoGuides publishes machine-use permissions and restrictions for supported public data so automated consumers can inspect the governing terms instead of inferring them from surrounding product copy.
✅
Machine-readable license metadata is live — supported public machine endpoints expose the GoGuides Data License and license version so automated systems can determine permitted use without having to infer licensing from surrounding page text.
✅
GoGuides Trust IDs are in use — domains can be represented by stable GoGuides trust identifiers, helping public trust records remain consistent across profiles, history pages, feeds, and evaluation endpoints.
✅
Source-use decision context is live — Evaluate can publish GoGuides decision context, basis, and limits for supported source-use categories while leaving the consuming system responsible for its own ranking, safety, citation, and source-use policy.
✅
Evaluate carries fuller source-use context — evaluate.php publishes supported GoGuides evidence, interpretation, policy context, basis, and limits, while signal.json remains a lighter discovery surface.
Derived evidence & analysis
✅
Batch Evaluate is live — supported clients can evaluate multiple exact URLs in one bounded request while preserving the authoritative per-URL resolver and scoring semantics used by individual evaluation.
✅
Claim Support is live — one claim can be analyzed against one fixed stored source observation through a bounded model-assisted contract that keeps source evidence distinct from derived analysis.
✅
Claim Support lifecycle and feedback are live — issued analyses can expose status and accept structured feedback without treating feedback as a vote that changes underlying evidence into truth.
✅
Content Relationships V1 is live — two exact URLs can be compared conservatively using stored evidence, with explicit unknown or abstaining states instead of inferring ownership, intent, or coordination.
Verified Text & source integrity
✅
Verified Text Search is live — GoGuides now has a dedicated
Verified Text Search page for hash-verified source records, topic lookup, direct chunk lookup, and JSON access for AI systems, RAG pipelines, crawlers, and developers.
✅
Britannica Verified Text Library is live — the crawlable
Britannica Verified Text Library exposes a large paginated collection of public-domain records with source metadata, canonical record URLs, and SHA-256 integrity metadata.
✅
Example verified record: 1911 Britannica gravity chunk — source: Encyclopaedia Britannica (1911), chunk ID:
1911:gravity:0001, SHA-256:
44295a1ecb5f31a5801ebcfac933b8b082c7828ee073c07a9fad47bba7e51558.
✅
Exact verified text can be locked to a hash — the gravity example verifies the text: “gravity is a natural phenomenon by which all things with mass are brought toward one another.”
✅
Verified-text bot search is live —
verified-text.php can return source-attributed topic previews as JSON, with canonical full-record URLs for deeper inspection.
✅
Substantial verified-text source collections are live — Open English WordNet, Encyclopaedia Britannica 1911, and Encyclopaedia Britannica 1926 records can be searched or browsed with source licensing, attribution, machine-use guidance, canonical record URLs, normalizer metadata, hash-scope metadata, and SHA-256 integrity values.
✅
Preview-first verified records reduce bot payload size — topic lookups can return bounded previews first, while full_record_url points machines to the canonical full verified text record when needed.
✅
Hash scope is explicit for verified text — GoGuides distinguishes preview snippets from full normalized text so bots know the SHA-256 integrity check applies to the complete normalized record, not a shortened preview.
Professional assessment & verifiable credentials
✅
AI Marketing Skills Assessment is live — the free 100-question assessment covers SEO fundamentals, AI search, AEO, GEO, crawler behavior, structured data, website trust, analytics, measurement, content quality, and technical signals.
✅
Timed scoring and category feedback are live — participants receive a 45-minute timer, randomized question order, an 80% passing threshold, category-level results, and explanations for missed answers.
✅
Privacy-first result handling is active — attempts are not added to the public certificate registry unless the participant passes and voluntarily requests a certificate.
✅
Free certificate issuance is live — passing participants can request a GoGuides AI Marketing Skills Certificate without registration or payment.
✅
Unique certificate IDs are live — each issued credential receives a structured GoGuides certificate ID tied to the assessment type, issue year, and a unique record identifier.
✅
Public certificate verification is live — each issued credential receives a permanent public record showing the participant, score, issue date, certificate status, and certificate ID.
✅
Certificate lookup is live — visitors can enter a certificate ID directly on the
assessment page to open its public verification record.
✅
Downloadable social certificate cards are live — valid credentials receive a database-generated 1200×630 share image with participant name, score, certificate ID, issue date, GoGuides branding, and QR verification.
✅
Printable certificate pages are live — certificate holders can open a formatted landscape certificate and use their browser to print it or save it as a PDF.
✅
QR-based verification is live — certificate cards connect viewers directly to the permanent public verification record through a scannable QR code.
✅
Certificate status and revocation support are built in — the registry stores valid, revoked, and related certificate-state information so invalid credentials can be rejected by the public verification page.
✅
Assessment discovery is integrated — the test, certificate lookup, verification records, share cards, and printable certificates are connected through GoGuides Navigation and the public assessment experience.
Everyday search features
✅
Modern search UI is live — GoGuides search results are mobile-friendly and built around quality, clarity, trust profile links, history links, AI Rank, and grade display.
✅
Site search operator is supported — dedicated handling for domain-specific searches helps users check whether a site is represented in the GoGuides index.
✅
Aggressive safety filtering is active — adult and gambling suppression rules help keep harmful or unwanted results out of ordinary search paths.
State, integrity & transparency
✅
Observed state and ownership verification are separated — GoGuides can report independently observed public state without treating proof of domain control as proof that the content itself is true, safe, or endorsed.
✅
Ownership-verification context is explicit — public reports can distinguish passive observation from accepted proof-of-control evidence without turning either state into a universal trust judgment.
✅
Public record surfaces expose supporting context — eligible records can expose rank, grade, observation timing, ownership-verification context, longitudinal history, and related machine-readable resources.
✅
Trust state is machine-readable — profiles, records, feeds, and evaluation endpoints expose structured signals instead of hiding trust behind a black-box score.
✅
Signal broadcasting is conservative — public feed visibility is intentionally limited to stronger trust states so the feed remains meaningful and does not become another noisy directory.