GoGuides Roadmap & Progress

GoGuides has moved beyond a simple search project. Today it includes an independent search index, live AI visibility checks, public trust profiles, verification history, machine-readable trust endpoints, favicon trust signals, and a public signal feed for stronger domains.

✅ Done ☑ In progress ☐ Planned High-level only

What this roadmap shows

This page is a public, high-level view of the GoGuides system as it stands today and where it is heading next. It avoids sensitive infrastructure details, but it does show the major public pieces now running.

Current direction GoGuides is being built as a search engine and trust layer for the AI internet: public trust profiles, verification history, AI visibility checks, bot activity signals, machine-readable endpoints, favicon trust signals, and a live signal feed.

What’s running live right now

Quick links
AI visibility checker · ChatGPT visibility checker · AI bot activity checker · evaluate JSON · signal.json · example trust profile · example trust history · verify · submit site · live broadcast

Roadmap checklist

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 results combine relevance and trust signals — GoGuides is not only matching keywords; it is building toward results that consider quality, freshness, trust state, and observed domain behavior.
✅
Site operator and safety filters are improving — special search paths and aggressive filtering help keep harmful, irrelevant, or low-value results from leaking into user-facing search.
✅
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.
✅
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.
✅
Front-door quality demotion is active — parked domains, domain-for-sale pages, recovered demo sites, stale make-money pages, and group-link farms are now capped below the public listing threshold before they can receive positive search visibility.
✅
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.
☑
Quality cleanup continues — ongoing tuning removes irrelevant entries, oversized titles, bad suggestions, encoding artifacts, and other search-result noise as the index grows.
☑
Freshness and recrawl logic are evolving — GoGuides is moving toward smarter refresh behavior that keeps active domains fresh without wasting crawl resources on stable evergreen pages.
☐
Broader language and source expansion — future growth will widen coverage only after ranking controls, spam suppression, and trust-layer guardrails remain stable.
☐
Deeper search personalization controls — future user settings may allow safer preferences around thumbnails, result layout, safe search behavior, and domain-level trust display.

Signals & learning loop

✅
Search impressions and user-facing signals are being captured — GoGuides records what is shown, saved, reported, clicked, or revisited so future ranking can be informed by real-world behavior instead of static assumptions.
✅
Public signal feed is live — stronger domains can appear in a live machine-readable feed that exposes selected trust signals to humans, bots, and future AI-facing consumers.
✅
Bot activity can be tied back to trust endpoints — GoGuides records when systems request or revisit trust-layer endpoints, helping show whether a domain is being checked by automated systems.
✅
Trust timeline signals are visible — reports can show first seen, last observed, observation count, days observed, trust record age, stability window, current trust state since, and rank/algo state changes.
✅
Verification fingerprints are live — GoGuides can expose SHA-256 trust-state fingerprints so public trust records become more machine-readable and easier to compare over time.
☑
Domain-level aggregation continues — page-level signals, rank data, crawl freshness, verification state, and bot activity are being shaped into clearer domain-level trust records.
☑
Signal quality controls are tightening — GoGuides is keeping signal broadcast conservative so public feeds remain meaningful instead of becoming another noisy directory.
☐
Abuse-resistant learning layer — future ranking feedback will need rate limits, anomaly checks, and manipulation resistance before broader automated tuning is trusted.
☐
Safe auto-tuning — long-term, GoGuides may tune search weights from real signals, but only after guardrails, review paths, and rollback controls are proven.

Webmaster & SEO experience

✅
Submission pipeline is live — domains can be submitted directly into GoGuides for evaluation, indexing eligibility, and trust-state creation.
✅
User submissions receive priority handling — newly submitted URLs are pushed into a faster crawl path so site owners do not wait behind lower-value background crawl work.
✅
AI visibility checker pages are live — GoGuides now has public pages that answer high-intent webmaster questions: whether a site is used by AI, why it may not show in ChatGPT, and whether AI bots are visiting.
✅
Tool-backed reports are live — those pages do not just explain the problem; they let a site owner enter a domain and receive a live trust-layer report based on GoGuides data.
✅
Unverified-state warnings are active — reports now clearly show when a domain is known but unverified, active but unverified, or missing public trust-layer signals entirely.
✅
Observed vs active states are separated — GoGuides can distinguish between a domain that has been seen, a domain with public trust data, and a domain that has completed stronger verification/activation steps.
✅
Verified trust button system is live — domain owners can expose a public trust button tied to their GoGuides Trust Profile and public history record.
☑
User panel and activation flow continue improving — free preview, activation, verification, activated-domain services, and trust-feed participation are being shaped into a clearer webmaster path.
☑
Activated-domain value layer is expanding — activated domains are intended to receive stronger services such as verification, trust broadcasting, topics, descriptions, usage-limit lifts, and richer public/API signals.
✅
One-time Trust Signal Activation model is clarified — GoGuides now separates free submission, account claim, and domain activation so users can understand exactly what is free, what is activated, and what does not affect organic ranking.
✅
Primary Topic selection is live — activated domains can declare one high-level topic that helps organize public trust metadata and future machine-readable trust outputs.
✅
Site Keywords selection is live — activated domains can choose up to three crawler-detected keywords without free-form keyword stuffing or paid-link confusion.
✅
Public activation wording has been cleaned up — public help, policy, roadmap, trust-profile, privacy, and terms pages have been aligned around Trust Signal Activation instead of old plan or recurring-payment language.
☐
Full webmaster controls and API access — future account tools will provide deeper control over verification, signals, monitoring, trust visibility, and developer-facing access.

Favicon trust signal system

✅
Deterministic favicon signal is live — GoGuides generates repeatable trust-linked favicon previews tied to measured domain state, AI Rank, crawl timing, and canonicalized domain signals.
✅
Public trust surfaces are connected — favicon trust signals now connect with Trust Profiles, Trust Records, verification history, and public domain history pages.
✅
Verified trust button system is live — site owners can display compact GoGuides trust buttons that point users and machines back to public trust records.
✅
Visual trust state is tied to measured history — favicon state now sits alongside rank, grade, crawl freshness, verification fingerprints, and observed trust changes over time.
☑
1:1 favicon consistency work continues — GoGuides is moving toward exact consistency between generated favicon states across favicon endpoints, search results, trust profiles, and public embeds.
☑
Machine-readable favicon identity is evolving — future favicon work may include stronger seed consistency, hidden verification cues, tamper-resistant markers, and compact visual proof signals.
☐
Trusted favicon network interactions — longer-term work may allow trusted sites to recognize related trust signals through lightweight client-side code without constant server callbacks.
☐
Expanded public trust badge system — the favicon, trust button, and public history record will continue evolving into a stronger website identity and trust layer.

Trust layer & 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 — domains can expose a human-readable and machine-readable profile showing observed state, activation status, trust signals, and public verification context.
✅
Evaluate endpoint is machine-readable — GoGuides can return structured JSON for domain trust checks, including trust ID, source type, observed state, public eligibility, activity signals, freshness, related URLs, and verification status.
✅
Trust timeline and fingerprinting are live — first seen, last observed, observation count, days observed, stability window, state changes, and SHA-256 verification fingerprints help turn trust into measurable public state.
✅
Public signal feed is live — stronger domains that meet trust thresholds can be broadcast as a machine-readable signal for humans, bots, and future AI-facing consumers.
✅
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.
☑
Trust primitive direction is defined — GoGuides is being shaped as a minimal, deterministic, machine-readable trust layer that other systems can query, inspect, and build on.
☑
Machine-use source clearance is being defined — GoGuides is moving toward structured machine-use decisions that distinguish whether a source may be read, summarized, cited, recommended, used for transactions, or used for sensitive advice.
☐
Evaluate endpoint will carry the fuller source-clearance record — the detailed machine-use basis belongs in evaluate.php, while signal.json should remain a lightweight broadcast pointer for machines.
☐
Signal feed cleanup will reduce machine ambiguity — future feed output should avoid unnecessary null values, separate observed quality from verified identity, and publish compact machine-use summaries without overclaiming trust.
☑
Shared decision enforcement is expanding — GoGuides is aligning crawler, search, evaluate, trust profiles, badges, signal feeds, and promotion systems so blocked or locked domains cannot receive positive trust exposure.
☑
Trusted data layer groundwork continues — hashing, source classification, provenance checks, and authoritative reference-data verification remain part of the long-term trust-layer plan.
☐
Expanded trust and provenance API — future developer and commercial API access can expose richer verification, history, source-type, provenance, and bulk trust-check data beyond the public feed.

Verified Knowledge & Trusted Data Layer

✅
Verified text proof-of-concept is live — GoGuides can show a source, stable chunk ID, SHA-256 fingerprint, and exact verified text for a trusted knowledge excerpt.
✅
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 for bots and developers, with canonical full-record URLs for deeper inspection.
✅
Verified-text sources now include OEWN and Britannica — Open English WordNet, Encyclopaedia Britannica 1911, and Encyclopaedia Britannica 1926 records can be surfaced with source licensing, attribution, machine-use guidance, and hash-scope metadata.
✅
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.
☑
Quote drift and tampering can be detected — if a single character in a verified text chunk changes, its SHA-256 fingerprint changes, making silent edits, corrupted references, or altered quotations easier to catch.
☑
AI systems can reference fixed source objects — a model, agent, or developer can store a source key, chunk ID, and hash, then later verify that it is still pointing to the same exact text.
☐
Verified knowledge API — future API access could allow AI systems and developers to query verified chunks, provenance records, source types, fingerprints, and exact trusted text for safer citation and retrieval.
☐
Machine trust beyond websites — this expands GoGuides from domain trust into source trust, content trust, and verifiable knowledge objects that AI systems can use directly.

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.
☑
Quick answers and definitions are improving — GoGuides is cleaning up answer boxes, removing wiki-markup artifacts, and improving reliability for definition-style searches.
☑
Spelling and suggestion quality is being tuned — suggestions are being improved to avoid bad jumps, unrelated terms, or misleading nearby-word matches.
☑
Search-result cleanup continues — GoGuides is working through encoding issues, oversized titles, irrelevant music/slop results, and low-value pages that weaken result quality.
☐
User customization — future settings may include layout preferences, safe-search behavior, saved-result controls, and other opt-in user experience choices.
☐
Search results thumbnail preference — thumbnails are planned as a user preference with classic/no-thumbnail layout as the default.
☐
Deeper AI Q&A integration — future work can connect search results, trust profiles, and AI-assisted exploration more tightly.

Trust, integrity & transparency

✅
Observed and verified states are separated — GoGuides can show that a domain is known or observed without pretending it is verified. Verified status remains a stronger trust state.
✅
Unverified warnings are explicit — public reports now make it clear when GoGuides can see a domain but cannot confirm ownership or verified trust status.
✅
Public trust records are transparent — observed domains can expose rank, grade, crawl timing, verification history, trust timeline data, and machine-readable trust context.
✅
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.
✅
User-first ranking direction is protected — GoGuides is designed around quality and trust signals, not selling search placement or letting paid listings override neutral results.
☑
Policy guardrails are expanding — spam controls, harmful-category suppression, public/private state separation, and rate-limit protections continue to harden the trust layer.
☑
Verification and provenance alignment continues — trust profiles, history records, favicon signals, signal feeds, and future APIs are being aligned into one consistent public trust model.
☑
Answer-box source layer is being assembled — GoGuides is preparing trusted reference sources such as Webster’s 1913, Britannica 1911, and arXiv computer-science records to support source-backed answers and future AI-facing direct-answer APIs.
☐
Expanded public trust API — future work will expose deeper verification, provenance, historical trust, source-type, and bulk-check data to developers and commercial users.
✅ Completed
Already running live on GoGuides today.
☑ In progress
Internal work has started; still being refined.
☐ Planned
Next steps we intend to build, after prerequisites are stable.
High-level only
No sensitive infrastructure details are published here.