SEO report for localplot.in

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 localplot.in…

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://localplot.in/sitemap_index.xml listing 16 sitemaps.

  Declared in robots.txt.

  Most recent lastmod: 2026-11-11T10:34:34+00:00.

• ✓

  Canonical URLhigh

  Canonical: https://localplot.in/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.localplot.in redirects to localplot.in.

Search snippet & sharing 54%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Homepage - Local Plot”

  About 203px 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.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✗

  Meta descriptionhigh

  No meta description – Google will pick text from the page.

  Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en-US"

Content quality 53%

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

• ✓

  Word countmedium

  1,732 words of main content (inside <main>).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

• ✓

  Readabilitymedium

  Flesch reading ease 62 (plain English), about 8 words per sentence.

• !

  Topic focushigh

  2 of 3 title keywords appear in the main content (missing: homepage).

  Fix: Use your main title phrases naturally in the opening paragraph and headings.

  Find the phrases people search with the free keyword generator

  Read the guide: how to write SEO content

• !

  H1 headingcritical

  “We help people buy, rent and sell homes”

  The H1 shares no keywords with the title.

  Fix: Use one H1 that states the page topic with its main keyword.

• ✗

  Heading structuremedium

  66 headings for 1732 words – a lot for the amount of text.

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

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

  Read the guide: the on-page SEO checklist

• ✗

  Text-to-code ratiolow

  3% of the HTML is visible text.

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

AI search readiness 78%

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. “Interested in selling your home?”.

  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.

  1 official profile link(s) (sameAs).

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

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• ✓

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

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

Structured data 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  131 internal and 21 external links.

• ✗

  Anchor text qualitymedium

  Same text used for different pages: “blog”, “view listings”, “continue reading”.

  4 link(s) with no text at all.

  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 47%

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

• ✓

  Server response (TTFB)high

  428 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

  409 kB of HTML – heavy for phones.

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

• ✓

  Compressionmedium

  Compressed with gzip.

• ✗

  Render-blocking resourceshigh

  2 blocking script(s) and 2 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

  29 script tag(s); files loaded from 5 other domain(s): fonts.googleapis.com, googletagmanager.com, accounts.google.com, js.hs-scripts.com, js.hsforms.net.

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

  Read the guide: Core Web Vitals

• !

  Imagesmedium

  46 image(s).

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

  12 image(s) after the first three aren't lazy-loaded.

  21 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: no-cache

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• ✓

  HTTP/3low

  Server advertises HTTP/3 (faster on mobile networks).

Security 67%

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: CSP.

  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

  X-Powered-By reveals “PHP/8.1.34”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 75%

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

• ✓

  Mobile viewportcritical

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

• ✓

  Image alt textmedium

  All 46 images have alt text.

• ✗

  Form labelsmedium

  78 of 98 form field(s) have no label.

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

• ✗

  Link nameslow

  4 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✓

  Tap-to-contactmedium

  One-tap contact: phone and email.

Local SEO 33%

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

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

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

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  No postcode found (fine for service-area businesses).

  An email link is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist