Comparepedia roadmap: completed improvements and next priorities
This living roadmap separates completed work from planned experiments so readers can see what the site supports today and what still requires validation.
What has shipped
Comparepedia now uses true 404 responses for unavailable pages, quality-based indexing controls for incomplete comparisons, stable canonical URLs, and a focused sitemap instead of publishing every possible search combination.
The current public experience supports English. Earlier experimental language parameters now resolve to the English canonical version rather than being promoted as complete translations.
What comes next
The next priorities are more reliable entity matching, clearer correction workflows, deeper original research guides, and better explanations when one source is unavailable or ambiguous.
Multilingual pages and embeddable cards remain possible future projects, but they will not be released as indexable pages until the content, attribution, consent, and maintenance requirements are satisfied.
Why this roadmap was revised
The original roadmap described experiments as if they were imminent product commitments. That wording became outdated and could mislead readers about multilingual support and embeddable features. This revision turns the page into a living record that separates completed improvements, active maintenance, and ideas that have not yet passed review.
A public roadmap should increase accountability rather than create marketing noise. Dates and priorities can change when upstream services, search requirements, privacy obligations, or user evidence changes. We therefore explain the decision criteria behind each priority and avoid promising a feature merely because it would create more pages.
Completed: stronger indexing controls
Comparison pages now use source availability, source URLs, errors, and minimum usable text as quality signals. Incomplete pages can remain accessible while carrying a noindex directive. Truly unavailable topics return a proper 404 instead of a soft error page that search engines could mistake for content.
The sitemap is deliberately selective. It includes curated comparisons, topic directories, editorial guides, and trust pages rather than every search result that the application can generate. Canonical URLs consolidate duplicate parameters, and unsupported language variants are no longer promoted as standalone translated pages.
Completed: safer source handling
Source requests run with timeouts, caching, error handling, and limited retry paths. Grokipedia parsing checks for missing-page indicators and uses metadata only when it represents usable source content. Wikipedia requests retain canonical source links and can retry ambiguous labels when an entity needs clarification.
These changes reduce false availability, repeated upstream traffic, and pages built from error messages. They do not eliminate every mismatch, so curated entity overrides and reader correction reports remain important parts of the maintenance process.
Current priority: entity accuracy
Ambiguous search terms are the largest remaining editorial risk. The same label can refer to a business, product, scientific concept, person, or disambiguation page. We are reviewing popular topics, strengthening explicit mappings, and checking whether the displayed source title matches the user intent expressed by the page slug.
The target is not perfect automation. High-value topics should receive human review, and a questionable result should be withheld from indexing until the mapping is dependable. Correction reports with a URL and supporting source help prioritize errors that affect real readers.
Current priority: deeper original guidance
Dynamic excerpts make source differences visible, but they are not enough on their own. Editorial guides are being expanded around concrete reader tasks such as verifying an AI-generated claim, comparing citations, recognizing omitted context, and deciding when a primary source is necessary.
New guides must add a distinct workflow or analysis rather than restate an encyclopedia summary. Topic directories will connect those guides to relevant comparisons so readers can move from general instruction to a specific example without encountering mass-produced doorway pages.
Current priority: trust and accessibility
Contact, editorial policy, privacy, attribution, methodology, and terms pages make ownership and responsibility easier to understand. The correction workflow is being made more visible, and advertising disclosures are being prepared before monetization so commercial code does not arrive ahead of user protections.
Accessibility work includes semantic headings, readable tables, descriptive link labels, keyboard-friendly controls, responsive layouts, and clear states when a source is unavailable. These are product-quality requirements, not decorative additions.
Deferred: translated and embedded experiences
A translated interface is not the same as translated content. A future language version would need genuinely localized editorial text, appropriate source selection, an accurate document language, self-referencing canonicals, reciprocal hreflang links, and translated policies. Until those requirements can be maintained, English remains the supported public language.
Embeddable cards are also deferred. Reuse must preserve source attribution, avoid creating duplicate low-value pages, respect privacy and consent choices, and remain understandable outside the full Comparepedia interface. No release date will be assigned until those constraints have a tested solution.
Ideas move from deferred to active only after the user need, maintenance owner, source rights, privacy impact, accessibility behavior, and quality checks are documented. This prevents a public experiment from becoming an unsupported promise or a collection of pages that no longer serves readers.