How accurate is the score?

Every check is based on what Google and the AI providers document publicly, and title widths are measured in pixels the way Google displays them. The score is a guide to how well-prepared a page is – no tool can guarantee rankings, because Google also weighs links, competition and many other signals.

Do you store my website's content?

No. We fetch the page like a search engine would, analyse it and keep only the finished report in a short-lived cache for an hour so repeat views are fast.

Is there a limit on how many sites I can check?

Not for normal use. The instant tools run in your browser and are unlimited. Full checks and audits only have a safety limit set far above what a person can use by hand (two checks a minute, every minute), plus a cap on how often any one website can be checked – that stops bots using XKey to flood other people's sites.

Do I need to give my email address?

No. XKey never asks for an email, an account or card details – not even for weekly monitoring, which gives you a private link instead.

Can I download my SEO report without signing up?

Yes. Use "Print or save as PDF" at the bottom of any report. The website audit also gives you a PDF and a CSV of every page, with no sign-up.

Can I check a competitor's website?

Yes – any public website. To see your site and up to two competitors side by side, use the competitor comparison.

Why is my score different from other SEO checkers?

Each tool weights different checks. XKey gives extra weight to things that stop a page appearing at all (indexing, titles, H1) and adds AI search readiness, which most checkers don't measure yet.

SEO report: www.archdaily.com scores 72/100

Fix these first

H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
See the details
Render-blocking resourceshigh
0 blocking script(s) and 5 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
Read the guide: Core Web Vitals
See the details
Mobile viewportcritical
viewport: width=device-width, initial-scale=1, maximum-scale=1, minimum-scale=1, user-scalable=no – blocks pinch-zoom
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
Read the guide: mobile-friendly websites
See the details
Readabilitymedium
Flesch reading ease 24 (difficult), about 12 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
Read the guide: how to write SEO content
See the details
Trust pages (E-E-A-T)medium
No links found to about, contact or privacy pages.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
See the details
HTML sizemedium
977 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
See the details
Imagesmedium
112 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
Read the guide: image SEO
See the details
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
Read the guide: the technical SEO checklist
See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to archdaily.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

✓
Status codecritical
The page returned HTTP 200.
✓
Indexablecritical
No noindex instruction – the page can appear in search.
✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
✓
XML sitemaphigh
Sitemap index found at https://www.archdaily.com/sitemap.xml listing 54 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-11-01T04:23:42+00:00.
✓
Canonical URLhigh
Canonical: https://www.archdaily.com/
Points to this page (self-referencing).
✓
Redirectshigh
1 redirect before the page loaded.
https://archdaily.com/ → https://www.archdaily.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
✓
www / non-wwwmedium
archdaily.com redirects to www.archdaily.com.

Content quality 47%

Is there enough clear, useful text that matches what the page targets?

✓
Word countmedium
2,266 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
✗
Readabilitymedium
Flesch reading ease 24 (difficult), about 12 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
Read the guide: how to write SEO content
✓
Topic focushigh
3 of 3 title keywords appear in the main content.
✗
H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
✓
Heading structuremedium
30 headings for 2266 words.
Levels are in order.
✗
Text-to-code ratiolow
3% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 75%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
Make one with the free llms.txt generator
Read the guide: do you need llms.txt?
!
Question-led contentmedium
1 heading(s) phrased as questions, e.g. “Did you know?”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
Read the guide: how to write SEO content
✓
Entity clarityhigh
Identified as: Organization.
7 official profile link(s) (sameAs).
✓
Freshness signalsmedium
The page shows when it was published or last updated.
✗
Trust pages (E-E-A-T)medium
No links found to about, contact or privacy pages.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 100%

Machine-readable facts for rich results and AI.

✓
JSON-LD present & validhigh
2 JSON-LD block(s): Organization, PostalAddress, WebSite, SearchAction.
All blocks parse correctly.
✓
Required propertiesmedium
Key types include Google's required properties.
i
Breadcrumbslow
Home page – breadcrumbs not needed.

Links 69%

Internal linking, anchor text and broken links.

!
Internal linkinghigh
296 internal and 3 external links.
Fix: Link to your most important pages from this page with descriptive text.
Read the guide: internal linking
!
Anchor text qualitymedium
Same text used for different pages: “© pol viladoms”, “2024”, “read more »”, “© juan camilo roa”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
Check every link's wording with the free anchor text checker
Read the guide: internal linking
✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.

Performance 37%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

!
Server response (TTFB)high
1143 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.
✗
HTML sizemedium
977 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
✓
Compressionmedium
Compressed with gzip.
✗
Render-blocking resourceshigh
0 blocking script(s) and 5 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
Read the guide: Core Web Vitals
!
Scripts & third partiesmedium
19 script tag(s); files loaded from 9 other domain(s): fonts.gstatic.com, fonts.googleapis.com, assets.adsttc.com, afd.adsttc.com, nrd.adsttc.com, cdn.viously.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
Read the guide: Core Web Vitals
✗
Imagesmedium
112 image(s).
24 without width/height – can cause layout shift (CLS).
99 image(s) after the first three aren't lazy-loaded.
0 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
Read the guide: image SEO
✓
Cachinglow
Cache-Control: max-age=0, public, s-maxage=3600
i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 75%

Visitor safety signals that browsers and Google check.

✓
HTTPScritical
Secure HTTPS with no mixed content.
✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
Read the guide: the technical SEO checklist
✗
Security headerslow
Present: Referrer-Policy.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
Read the guide: the technical SEO checklist
✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).

Mobile & accessibility 46%

Usable on phones and by everyone – Google indexes the mobile version.

!
Mobile viewportcritical
viewport: width=device-width, initial-scale=1, maximum-scale=1, minimum-scale=1, user-scalable=no – blocks pinch-zoom
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
Read the guide: mobile-friendly websites
✓
Image alt textmedium
All 112 images have alt text.
✗
Form labelsmedium
2 of 4 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
✓
Link nameslow
Every link has a readable name.
✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Read the guide: mobile-friendly websites

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

i
LocalBusiness markuphigh
No LocalBusiness structured data.
i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
i
Map & directionslow
No map or directions link.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

SEO report for www.archdaily.com

Fix these first

Real-world speed Google PageSpeed

Authority & backlinks

Indexing & crawling 100%

Status codecritical

Indexablecritical

robots.txthigh

XML sitemaphigh

Canonical URLhigh

Redirectshigh

www / non-wwwmedium

Search snippet & sharing 100%

Title tagcritical

Meta descriptionhigh

Open Graph & social cardsmedium

Faviconlow

Languagelow

Content quality 47%

Word countmedium

Readabilitymedium

Topic focushigh

H1 headingcritical

Heading structuremedium

Text-to-code ratiolow

AI search readiness 75%

AI crawler accesshigh

Snippet controlshigh

llms.txtlow

Question-led contentmedium

Entity clarityhigh

Freshness signalsmedium

Trust pages (E-E-A-T)medium

Structured data 100%

JSON-LD present & validhigh

Required propertiesmedium

Breadcrumbslow

Links 69%

Internal linkinghigh

Anchor text qualitymedium

Broken links (sample)high

Performance 37%

Server response (TTFB)high

HTML sizemedium

Compressionmedium

Render-blocking resourceshigh

Scripts & third partiesmedium

Imagesmedium

Cachinglow

HTTP/3low

Security 75%

HTTPScritical

HTTP → HTTPS redirecthigh

HSTSmedium

Security headerslow

Server fingerprintlow

Mobile & accessibility 46%

Mobile viewportcritical

Image alt textmedium

Form labelsmedium

Link nameslow

Tap-to-contactmedium

Local SEO not scored

LocalBusiness markuphigh

Contact details on pagemedium

Map & directionslow