SEO report for livepositively.com
https://livepositively.com/ · checked Sun, 01 Nov 2026 20:08 GMT
Fix these first
- Title tagcritical
“Writing Platform to Read & Publish Meaningful Articles | LivePositively”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.
- Heading structuremedium
55 headings for 700 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- Form labelsmedium
1 of 1 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.
- Open Graph & social cardsmedium
Open Graph title and image set.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
On WordPress: Yoast SEO and Rank Math add these tags for you. Set a sharing image in the plugin's Social tab on each page.
- Readabilitymedium
Flesch reading ease 39 (fairly difficult), about 16 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
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 livepositively.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://livepositively.com/sitemap.xml listing 3 sitemaps.
Declared in robots.txt.
No lastmod dates – add accurate ones so search engines know what changed.
- ✓
Canonical URLhigh
Canonical: https://livepositively.com
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.livepositively.com redirects to livepositively.com.
Search snippet & sharing 71%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Writing Platform to Read & Publish Meaningful Articles | LivePositively”
About 620px of Google's ~580px desktop width – it will probably be cut off.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.
- ✓
Meta descriptionhigh
159 characters, ~967px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 73%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
700 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 39 (fairly difficult), about 16 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
6 of 6 title keywords appear in the main content.
- ✓
H1 headingcritical
“Read and Publish Meaningful Articles That Inspire Positive Change”
- ✗
Heading structuremedium
55 headings for 700 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
2% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 81%
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.
Training-only crawlers blocked: CCBot, meta-externalagent. That's a licensing choice – these companies document them as separate from their search crawlers.
- ✓
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
18 heading(s) phrased as questions, e.g. “How to Balance the Life You Want With the Money You Have”.
- ✓
Entity clarityhigh
Identified as: Organization.
4 official profile link(s) (sameAs).
- ✗
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 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): Organization, ImageObject, PostalAddress, ContactPoint, WebSite, WebPage, Thing, FAQPage, Question, Answer, ItemList, ListItem.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
50 internal and 4 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 79%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
141 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
296 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 1 stylesheet(s) in <head>.
- !
Scripts & third partiesmedium
12 script tag(s); files loaded from 1 other domain(s): googletagmanager.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
19 image(s).
All images reserve their space.
8 image(s) after the first three aren't lazy-loaded.
15 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.
On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.
- ✓
Cachinglow
Cache-Control: s-maxage=3600, stale-while-revalidate
- ✓
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.
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✗
Server fingerprintlow
X-Powered-By reveals “Next.js”.
Fix: Remove X-Powered-By so attackers can't see your software versions.
Mobile & accessibility 67%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width
- ✓
Image alt textmedium
All 19 images have alt text.
- ✗
Form labelsmedium
1 of 1 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.
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.