Website profiles · Technology insights · Alternatives

consensus.app No paid content found

Categories: Artificial Intelligence

Consensus is an AI academic search engine for peer-reviewed literature—your research OS for finding, organizing, and analyzing science 10x faster.

Visit website

Updated: 2026-09-24 01:57 Language: English (default) Access: Normal

Profile views 0 Outbound visits 0
Consensus Full homepage screenshot

Related questions

More questions →
How Search Engines Find, Crawl, and Rank Pages: A Practical SEO Workflow

Search engines work in three separate stages: discovery, crawling/indexing, and ranking. A page can fail at any one of them, and each failure has a different fix. If your page isn't showing up, the fastest path is to check the stages in order — don't jump straight to "ranking factors" before you've confirmed the page is even indexed.

This guide walks through each stage, what blocks it, and a step-by-step diagnostic sequence you can run with free tools.

Stage 1: Discovery — How Search Engines Find Your URLs

Before a search engine can crawl a page, it has to know the URL exists. There are four main discovery paths:

  • Links from other sites (external backlinks)
  • Internal links from pages already known to the search engine
  • XML sitemaps you submit
  • Redirects and canonical signals pointing to the URL

What blocks discovery

  • Orphan pages: no internal links point to them, and no sitemap includes them. These are effectively invisible.
  • Sitemap errors: a sitemap that lists non-canonical URLs, returns errors, or isn't referenced in robots.txt.
  • Noindex on linked pages: if the only page linking to your target is itself excluded, the crawler may never follow the path.

Practical fix

  1. Add at least one contextual internal link from a page that is already indexed.
  2. Confirm the URL appears in your XML sitemap and that the sitemap is submitted.
  3. Check robots.txt doesn't disallow the path.

Stage 2: Crawling and Indexing — Getting the Page Stored

Crawling means the bot fetches the page. Indexing means the content is stored and eligible to appear in results. These are not the same thing — a page can be crawled but not indexed.

Common crawl blockers

Blocker Where it lives Effect
Disallow rule robots.txt Bot won't fetch the URL
noindex meta tag Page <head> Page fetched but excluded from index
X-Robots-Tag: noindex HTTP header Same as above, applies to non-HTML files
Login wall / paywall Server Bot sees a different page than users
Slow or erroring server Hosting Crawl budget wasted, page may be dropped

Common indexing blockers (page is crawled but not stored)

  • Thin or duplicate content: near-identical to another URL on your site.
  • Canonical tag pointing elsewhere: you're telling the engine "index that page instead."
  • Soft 404: page returns 200 but looks empty or error-like.
  • Wrong canonical chosen by the engine: often caused by conflicting signals (sitemap says A, canonical says B).

How to check index status

Use a site: query in the search engine (for example, site:example.com/page) as a rough check. It's not exact, but it tells you whether the URL is in the index at all. For a more structured view, use the search engine's own webmaster console if you have one — that's the authoritative source for coverage status.

Stage 3: Ranking — Why an Indexed Page Still Doesn't Appear

Once a page is indexed, ranking depends on relevance and authority signals. The main on-page levers:

Title and headings

  • The title tag is still one of the strongest relevance signals. Put the primary topic near the front.
  • H1 and subheadings should reflect what the page actually covers, not keyword-stuffed variants.
  • Mismatch between title and body content is a common reason a page ranks for nothing.

Content depth and intent match

  • Does the page answer the question the searcher is asking? A page about "search engines" that only defines the term will lose to a page that explains crawling, indexing, and ranking.
  • Cover the subtopics a searcher would expect. Thin coverage on a broad topic rarely ranks.

Internal links and authority

  • Internal links pass context and relative importance. A page with no internal links is treated as low priority.
  • External backlinks still matter, but quality and relevance outweigh raw count.

Technical signals

  • Mobile rendering: if the mobile version hides content, rankings suffer.
  • Core Web Vitals: page experience is a tiebreaker, not a primary driver, but poor performance can hurt.
  • HTTPS and clean URL structure: baseline expectations.

A Step-by-Step Diagnostic Sequence

Run these in order. Stop when you find the failure point.

  1. Is the URL in the index? Run site:yourdomain.com/page. If nothing appears, go to step 2. If it appears, skip to step 5.
  2. Is it blocked by robots? Check robots.txt for a Disallow rule matching the path. Check the page's meta robots and HTTP X-Robots-Tag.
  3. Is it discoverable? Confirm the URL is in your sitemap and has at least one internal link from an indexed page.
  4. Is it canonicalized elsewhere? Check the rel="canonical" tag. If it points to a different URL, that URL is the one being indexed.
  5. Is it indexed but not ranking? Compare your title and H1 against the query. Check whether the page covers the subtopics the top results cover.
  6. Check backlinks and keyword position. Free tools like the ones on SmallSEOTools.com can give you a backlink overview and keyword position tracking. Treat these as directional signals, not precise measurements — free backlink and rank tools typically sample data and can differ from what a search engine's own console reports.

Common Misconceptions

"Submit the URL and it indexes instantly." Submission queues a crawl; it doesn't guarantee indexing or timing. Indexing can take hours to weeks depending on the site.

"Meta keywords help ranking." They've been ignored by major search engines for years. Don't spend time on them.

"I can guarantee a #1 ranking." No tool or service can guarantee a specific position. Rankings depend on competition, query, location, and personalization. Anyone promising a fixed position is overstating what's controllable.

"More backlinks always means better rankings." Low-quality or irrelevant links can be ignored or actively harmful. Relevance and trust matter more than volume.

"If it's indexed, it should rank." Indexing is eligibility, not promotion. A page can be indexed and still rank on page 10 because it's less relevant or less authoritative than competitors.

Quick Reference: Which Stage Is Failing?

Symptom Likely stage First check
URL not in site: results Discovery or crawling robots.txt, internal links, sitemap
Crawled but not indexed Indexing Canonical tag, content uniqueness, meta robots
Indexed but ranks poorly Ranking Title/H1 match, content depth, internal links
Ranked, then dropped Crawling or ranking Server errors, content changes, lost links

Work through the stages in order. Most "my page won't rank" problems turn out to be discovery or indexing problems, and those are usually the fastest to fix.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2020, this domain has about 6 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is Squarespace Domains II LLC., a widely used domain service provider. The domain uses the common .app extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Google Workspace email service. DNSSEC is enabled, allowing validating resolvers to authenticate signed DNS data. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

X-Powered-By exposes backend information: Next.js. The response lacks these common security headers: HSTS, CSP, X-Content-Type-Options, Permissions-Policy, clickjacking protection. The cf-ray, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies Next.js, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 26 characters, within a common display range. A meta description is present, with 146 characters. No Generator meta tag is publicly exposed.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Location Location unknown 104.26.4.198

User reviews (0)

  • No reviews yet.

Pages, Search and Sharing

Meta descriptionConsensus is an AI academic search engine for peer-reviewed literature—your research OS for finding, organizing, and analyzing science 10x faster.
Canonical URLhttps://consensus.app/search/
LanguageEnglish (default)
Twitter Cardsummary_large_image
All bots 1 allowed · 4 disallowed
  • Allow/home/wp-content/uploads/
  • Disallow/home/wp-content/plugins/
  • Disallow/home/wp-admin/
  • Disallow/home/readme.html
  • Disallow/blog/
  • IntervalCrawl delay 1 seconds
oai-searchbot 1 allowed · 0 disallowed
  • Allow/
chatgpt-user 1 allowed · 0 disallowed
  • Allow/
perplexitybot 1 allowed · 0 disallowed
  • Allow/
perplexity-user 1 allowed · 0 disallowed
  • Allow/

Registration details RDAP / WHOIS

RegistrarSquarespace Domains II LLC.
Registered2020-07-27
Expires2027-07-27
Domain statusclient delete prohibited、client transfer prohibited
Nameserversdeb.ns.cloudflare.com、devin.ns.cloudflare.com
DNSSECsigned

DNS records

TypeNameValueTTLPriority
Aconsensus.app104.26.4.198260
Aconsensus.app104.26.5.198260
Aconsensus.app172.67.75.88260
AAAAconsensus.app2606:4700:20::681a:4c6300
AAAAconsensus.app2606:4700:20::681a:5c6300
AAAAconsensus.app2606:4700:20::ac43:4b58300
MXconsensus.appaspmx.l.google.com3001
MXconsensus.appalt1.aspmx.l.google.com3005
MXconsensus.appalt2.aspmx.l.google.com3005
MXconsensus.appalt3.aspmx.l.google.com30010
MXconsensus.appalt4.aspmx.l.google.com30010
NSconsensus.appdeb.ns.cloudflare.com83411
NSconsensus.appdevin.ns.cloudflare.com83411
TXTconsensus.appgoogle-site-verification=LPyQudxB2RpVXbhIK820Ez-o49xWXbKV-QePj9uUyRw300
TXTconsensus.appgoogle-site-verification=mZVfEU0a7IeGkQvzFwNnt2SqpiV0jBP0O9f6CjEfzpQ300
TXTconsensus.appnordpass-domain-verification=489137f87155cef6635822c24a818fbe6ebaa8c4091d516e5dcb32b0a56afbf3300
TXTconsensus.appopenai-domain-verification=dv-Zsp0xfmwmImFnBET5e0KDFyy300
TXTconsensus.appps-cd-verification=3f81fcad-ed51-4cc2-a050-66388736f7fb300
TXTconsensus.appv=spf1 include:47141966.spf03.hubspotemail.net include:_spf.google.com ~all300
CAAconsensus.app0 issue "comodoca.com"3600
CAAconsensus.app0 issue "digicert.com; cansignhttpexchanges=yes"3600
CAAconsensus.app0 issue "letsencrypt.org"3600
CAAconsensus.app0 issue "pki.goog; cansignhttpexchanges=yes"3600
CAAconsensus.app0 issue "ssl.com"3600
CAAconsensus.app0 issuewild "comodoca.com"3600
CAAconsensus.app0 issuewild "digicert.com; cansignhttpexchanges=yes"3600
CAAconsensus.app0 issuewild "letsencrypt.org"3600
CAAconsensus.app0 issuewild "pki.goog; cansignhttpexchanges=yes"3600
CAAconsensus.app0 issuewild "ssl.com"3600
DSconsensus.app2371 13 2 6061e57f0419aef22076ed823bdeeabfb7e6b37148322472afad317f65832c1c1800
DMARC_dmarc.consensus.appv=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc_aggregate_analyser+8a01f8c3602237c7b9f51af843dc70cb@zerobounce.net, mailto:[email protected]; ruf=mailto:dmarc_forensics_analyser+8a01f8c3602237c7b9f51af843dc70cb@zerobounce.net; pct=100; fo=1;300

TLS and certificates

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectconsensus.app
IssuerGoogle Trust Services
Valid until2026-12-15T11:32 · Remaining when checked: 82 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HeaderValue
content-typetext/html; charset=utf-8
cache-controlprivate, no-cache, no-store, max-age=0, must-revalidate
servercloudflare
referrer-policyorigin-when-cross-origin
set-cookieRedacted

Identified technologies

Next.jsCloudflare