SEO report

SEO report for www.rics.org

https://www.rics.org/ · checked Sun, 01 Nov 2026 14:05 GMT

Fix these first

  1. LocalBusiness markuphigh

    No LocalBusiness structured data.

    Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

    Also fixes: Entity clarity

    See the details

  2. JSON-LD present & validhigh

    No JSON-LD structured data.

    Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

    See the details

  3. Render-blocking resourceshigh

    2 blocking script(s) and 1 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

    See the details

  4. Title tagcritical

    “Welcome to RICS”

    Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

    See the details

  5. Question-led contentmedium

    No headings phrased as questions.

    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.

    See the details

  6. Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

    See the details

  7. Scripts & third partiesmedium

    42 script tag(s); files loaded from 3 other domain(s): cdn-ukwest.onetrust.com, assets.adobedtm.com, rics.scene7.com.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

    See the details

  8. Imagesmedium

    47 image(s).

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

    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 rics.org…

Indexing & crawling 94%

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 found at https://www.rics.org/sitemap.xml with 4,105 URLs.

    Declared in robots.txt.

    This page is listed in it.

    Most recent lastmod: 2026-10-30.

  • !

    Canonical URLhigh

    Canonical: https://publish-p192814-e2007676.adobeaemcloud.com/

    Points to a DIFFERENT address – Google will probably index that one instead of this page.

    The canonical points to a different website.

    Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://rics.org/ → https://www.rics.org/

    A single redirect to your preferred address is normal; just make sure your own links use the final address.

  • ✓

    www / non-wwwmedium

    rics.org redirects to www.rics.org.

Search snippet & sharing 79%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Welcome to RICS”

    About 159px of Google's ~580px desktop width – short; use the space.

    Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  • ✓

    Meta descriptionhigh

    130 characters, ~782px of ~990px.

    Good length.

    Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    No twitter:card tag.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="en"

Content quality 80%

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

  • ✓

    Word countmedium

    1,070 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 41 (fairly difficult), about 14 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  • ✓

    Topic focushigh

    1 of 1 title keywords appear in the main content.

  • ✓

    H1 headingcritical

    “Welcome to RICS”

  • !

    Heading structuremedium

    40 headings for 1070 words – a lot for the amount of text.

    1 skipped level(s), e.g. H2 → H4.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  • ✗

    Text-to-code ratiolow

    3% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 50%

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.

  • ✗

    Question-led contentmedium

    No headings phrased as questions.

    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.

  • ✗

    Entity clarityhigh

    No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  • ✗

    Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

  • ✓

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

    Links found to all three: about, contact and privacy.

Structured data 0%

Machine-readable facts for rich results and AI.

Performance 47%

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

  • ✓

    Server response (TTFB)high

    195 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  • !

    HTML sizemedium

    335 kB of HTML.

    Fix: Remove inline bloat, base64 images and unused markup.

  • ✓

    Compressionmedium

    Compressed with br.

  • ✗

    Render-blocking resourceshigh

    2 blocking script(s) and 1 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  • ✗

    Scripts & third partiesmedium

    42 script tag(s); files loaded from 3 other domain(s): cdn-ukwest.onetrust.com, assets.adobedtm.com, rics.scene7.com.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  • ✗

    Imagesmedium

    47 image(s).

    37 without width/height – can cause layout shift (CLS).

    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.

  • ✓

    Cachinglow

    Cache-Control: max-age=120, stale-while-revalidate=600

  • 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 96%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✓

    HSTSmedium

    HSTS: max-age=63072000

  • !

    Security headerslow

    Present: CSP, nosniff, clickjacking protection.

    Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  • ✓

    Server fingerprintlow

    No X-Powered-By header (server: cloudflare).

Mobile & accessibility 67%

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

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1

  • ✓

    Image alt textmedium

    All 47 images have alt text.

  • ✗

    Form labelsmedium

    2 of 2 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

  • ✗

    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.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

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

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.