A · Very good

Page SEO Inspection

https://theinbetweenself.com/
Crawled 16 Nov, 12:17 UTC (1 day ago)
HTTP 200 114 KB 691 ms TTFB
Download PDF

PDF export is a paid feature

A PDF of the full report, ready to send to a client or a colleague, comes with Basic at $19 a month and every plan above it, along with saved history. The report itself stays free to read.

See the plans
On-Page Checklist 85% Complete
Primary focus: Nothing prevents this page being embedded in a frame, which allows clickjacking. Fix now →
Filter:

Full diagnostics

Every check that ran, grouped by what it affects. Problems appear first in each group.

Meta Tags & Search Snippet Simulator

The tags that decide how this page is titled and described in search results.

i 1✓ 150% · fair
Live snippet simulation
Title width: 508px / 580px
T The In-Between Self theinbetweenself.com
The In-Between Self: Rebuilding Identity After Awakening

You're no longer who you were, but not yet who you're becoming. Take the free In-Between Self Assessment and find your archetype, conditioning, and…

Meta description 170 characters

The meta description is 170 characters, so search results will likely cut it short.

You're no longer who you were, but not yet who you're becoming. Take the free In-Between Self Assessment and find your archetype, conditioning, and stage of the crossing.
Title tag 508px of 580px

The title length is well judged.

Rendered width

Desktop508px/ 580px
Mobile457px/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 56.

Crawling & indexing

Whether search engines can reach, read and index this page at all.

! 1i 1✓ 1588% · good
Missing pages (404) HTTP 200

A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.

https://theinbetweenself.com/wrp-missing-9742f0f1d8 answered HTTP 200
How to fix
How to fix
Make the server or the application return a 404 status for unknown addresses. The not-found page can look the same; only the status code has to change.
www and https versions 1 found

The other spellings of this address arrive here, but not in one permanent step: a chain costs time on every visit, and a temporary redirect tells search engines the move may not last.

http://www.theinbetweenself.com/ → 301 → 308 → https://theinbetweenself.com/ (2 redirects)
How to fix
How to fix
Redirect each spelling straight to the final address with a 301 or 308.
HTTP status HTTP 200

The page returns 200 OK.

Redirect chain

The URL resolves without redirects.

Robots directives

No directive prevents indexing.

Canonical tag

The canonical correctly references this page.

https://theinbetweenself.com/
Language

Language is declared as "en".

lang="en"
hreflang

No hreflang annotations, which is correct for a single-language page.

Viewport

The viewport is configured for mobile.

width=device-width,initial-scale=1
Character encoding

The page declares UTF-8 encoding.

Favicon

A favicon is declared.

Mixed content

All resources load securely.

URL length 29 characters

The URL is 29 characters.

URL readability

The URL is clean and readable.

URL depth 0 levels deep

The page is 0 levels deep.

URL parameters

The URL has no query parameters.

robots.txt 0 KB

robots.txt is present and does not block crawling.

XML sitemap 2 URLs

A sitemap index is published, referencing 2 sitemaps.

Sitemap index referencing 2 sitemaps

Content & metadata

What the page says it is about, and how it reads.

✓ 11100% · excellent
Word count 2,327 Substantive
Headings 80 Structured
H1 tags 1 Exactly one
Text ratio 15.0% Text vs markup
Heading outline 80 headings
H1 You're no longer who you were, but not yet who you're becoming.
H2 Does This Feel Familiar?
H2 Locate yourself in the territory
H3 Your Archetype
H3 Your Conditioning
H3 Fear or Purpose
H3 Your Stage
H2 Five ways of moving through the in-between
H3 The Observer
H3 The Wanderer
H3 The Mystic
H3 The Builder
H3 The Phoenix
H2 The shape of the crossing
Open Graph tags

Open Graph tags are present.

Twitter card

twitter:card is set to summary_large_image.

H1 tag

The page has exactly one h1.

You're no longer who you were, but not yet who you're becoming.
Heading hierarchy

The heading outline descends in order.

Content length 2,327 words

The page has roughly 2327 words.

Text-to-HTML ratio 15.0% text

Text is 15.0% of the page source.

Table headers

No data tables on this page, so there are no columns to label.

Keyword placement

The page's prominent terms appear in its title, description or headings.

Where these terms appear

TermCountDensityTitleDescriptionHeadings
self452.90%✓✓✓
between362.32%✓✓✓
identity281.80%✓✕✓
awakening181.16%✓✕✓
through161.03%✕✕✓
Keyword repetition

No term is repeated unnaturally often.

Keyword cloud

The page's most frequent terms, from 1553 words of content.

What this page is about

Term size reflects how often it appears. Density is not a ranking factor, this is a view of the page's subject, not a target to hit.

selfbetweenidentityawakeningthroughsystemspiritualnervousisnfeelwithoutyettransformationauthenticlongeryourselfpatternsonceoldclaritylifewhereshadowawarenessfalsestateliminalfamiliarhereworkfeelssupportpracticesarchitecturedissolutionsomethingthresholdconditioningintegrationothers
Share image 1200 × 630 px

The share image loads and is 1200 × 630 pixels, the right size and shape for a large card.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

i 1✓ 990% · excellent
AI crawlers 10/10 All allowed
Readable without JS Yes Served complete
Identity 1/2 Partly declared
Quotable signals 4/4 Schema, date, author, answers
Page subject

FAQPage declared without a name or headline.

FAQPage
How to fix
How to fix
Give each of these a name, or a headline for an Article. The type says what kind of thing the page is about; without a name it does not say which thing.
Answer readiness 8 found

8 headings are followed by a snippet-shaped answer.

Content freshness

The page is dated and about 16 days old.

datePublished in structured data, dateModified in structured data, <time datetime>

Attribution

Attribution signals present: author in structured data, publisher in structured data, about page, privacy policy.

author in structured data, publisher in structured data, about page

Answer schema

Answer-friendly structured data: FAQPage, Question, Article.

FAQPage, Question, Article

3 types: FAQPage, Question, Article

Extractable structure 2,327 words

2327 words across 80 headings, 14 lists and 0 tables.

Publisher identity

The page names who is behind it: The In Between.

Readable without JavaScript

The page reads the same with and without JavaScript.

llms.txt for AI agents

llms.txt is published, giving AI agents a curated map of the site.

AI crawler access 10 checked

Every AI crawler checked is allowed to read this page.

Speed & delivery

What makes the page slow, and what the loading experience measures.

! 1✓ 1292% · excellent
Rendered page
The page as it rendered on a mobile viewport during the performance test
Mobile, measured
The page as it rendered on a desktop viewport
Desktop, measured
LCP Good
1.67s

Largest Contentful Paint

Target ≤ 2.5s

What this measures

How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".

What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.

INP Good
172ms

Interaction to Next Paint

Target ≤ 200ms

What this measures

How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.

What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.

CLS Good
0

Cumulative Layout Shift

Target ≤ 0.1

What this measures

How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.

What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.

FCP Good
1.67s

First Contentful Paint

Target ≤ 1.8s

What this measures

How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.

What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.

TTFBNo data
n/a

Real-user response time

Target ≤ 800ms

Needs real-user data from Chrome UX Report

Browser caching 123 KB re-downloaded

3 files have cache lifetimes short enough that returning visitors download 123 KB again.

Short cache lifetimes

FileCache lifetimeSize
ap.emergent.sh/array.js5m121 KB
assets.emergent.sh/emergent-main.jsnone6 KB
ap.emergent.sh/config.js5m2 KB

3 expire within the hour

How to fix
How to fix
Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.
Time to first byte

Time to first byte is 691 ms.

Render-blocking resources 2 found

2 render-blocking resources in the head.

HTML size 114 KB

The HTML document is 114 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 23 found

23 inline style attributes.

Compression

The response is compressed with gzip.

Content-Encoding: gzip
Page weight 11 requests · 459 KB

The page loads 11 requests totalling 459 KB.

What loaded, by type

Type RequestsTransferred
script6405 KB
document122 KB
stylesheet116 KB
image1of 11 declared14 KB
other21 KB

Of these, 7 requests (223 KB) come from third-party domains. The HTML declares 11 images but only 1 loaded, the rest are lazy-loaded and fetched when scrolled to.

Third-party services 2 services · 223 KB

2 third-party services load on this page, adding 223 KB.

Third-party services

Service TransferredMain thread
emergent.sh209 KB268ms
unsplash.com14 KBunder 1ms

0.3s of main-thread time

Security

Transport security, reputation and the response headers that protect visitors.

! 1i 3✓ 969% · fair
Clickjacking protection

Nothing prevents this page being embedded in a frame, which allows clickjacking.

How to fix
How to fix
Content-Security-Policy: frame-ancestors 'self'
Content Security Policy

No Content-Security-Policy, the main defence against cross-site scripting.

How to fix
How to fix
Content-Security-Policy: default-src 'self'
Permissions policy

No Permissions-Policy header, so any script or embed on the page may ask for the camera, microphone or location.

How to fix
How to fix
Permissions-Policy: camera=(), microphone=(), geolocation=()
security.txt

No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.

https://theinbetweenself.com/.well-known/security.txt
How to fix
How to fix
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
Email addresses in the page

No email addresses are written into the page for harvesting bots to collect.

HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=63072000; includeSubDomains; preload
MIME sniffing

MIME sniffing is disabled.

Referrer policy

Referrer-Policy is "strict-origin-when-cross-origin".

strict-origin-when-cross-origin
Cookie flags

All 2 cookies the page sets carry Secure, HttpOnly and SameSite.

Version disclosure

No software versions are disclosed in headers or the page.

TLS certificate 83 days left

The TLS certificate is valid for another 83 days, issued by Google Trust Services.

83 days remaining
Google Web Risk

Not listed by Google Web Risk for malware, phishing or unwanted software.

TLS version TLS 1.3

Connections use TLS 1.3.

Server & domain

The server and the domain behind the page: protocol, network, registration and email records.

i 3✓ 457% · fair
IPv6

theinbetweenself.com has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.

How to fix
How to fix
Add an AAAA record. Most hosts and every major CDN provide an IPv6 address.
SPF record

theinbetweenself.com has no SPF record, so nothing tells mail servers who may send email as this domain. Spoofed mail is easier, and genuine mail is likelier to land in spam.

How to fix
How to fix
Publish a TXT record starting v=spf1 that lists the services that send your mail. A domain that sends none: v=spf1 -all
DMARC policy

theinbetweenself.com has no DMARC record, so mail servers have no instruction for mail that fails SPF or DKIM. Gmail and Yahoo require one from bulk senders.

How to fix
How to fix
Publish a TXT record at _dmarc.theinbetweenself.com, starting with v=DMARC1; p=none; rua=mailto:[email protected] to collect reports, then tighten to quarantine or reject.
HTTP/2 HTTP/2

Served over HTTP/2, which loads a page's files in parallel over one connection.

CDN Cloudflare

Served through Cloudflare, a CDN, so visitors get the page from a server near them.

Domain expiry 213 days left

theinbetweenself.com is registered until 17 Jun 2027 with Cloudflare, Inc.

213 days remaining
Domain age Under a year old

theinbetweenself.com was registered on 17 Jun 2026, under a year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

ads.txt

No ad network loads on this page, so ads.txt is not needed.

Links, media & schema

Links, images and structured data.

! 1✓ 1192% · excellent
Social share preview From this page's Open Graph tags
Responsive images 3 found

3 large images are served at one fixed size, so phones download desktop-sized files.

# / lineImage source
#1 L1https://theinbetweenself.com/api/blog/media/0485b77a0deb634a087cf75eb9a64b77d1c623d94bf0b986cbd1b5121b8855c1.webp<img src="https://theinbetweenself.com/api/blog/media/0485b77a0deb634a087cf75eb9a64b77d1c623d94bf0b986cbd1b5121b8855c1.webp" alt="how to find yourself - A person writing in a notebook beside a window in soft natural light" width="800" height="450" loading="lazy" decoding="async" class="w-full h-ful…
#2 L1https://theinbetweenself.com/api/blog/media/c44356b9d256f34bd2b4f1bcc43f499d8051973772edba07defae6338c4fd1e9.webp<img src="https://theinbetweenself.com/api/blog/media/c44356b9d256f34bd2b4f1bcc43f499d8051973772edba07defae6338c4fd1e9.webp" alt="inner archetypes - A person looking through a window with their reflection visible in the glass" width="800" height="450" loading="lazy" decoding="async" class="w-full h…
#3 L1https://theinbetweenself.com/api/blog/media/904ef5029676301ef2386aa16b4398beca293efade69c81b9ccef28363aae8c9.webp<img src="https://theinbetweenself.com/api/blog/media/904ef5029676301ef2386aa16b4398beca293efade69c81b9ccef28363aae8c9.webp" alt="spiritual awakening checklist - A person writing in an open journal beside a softly lit window" width="800" height="450" loading="lazy" decoding="async" class="w-full h-…
How to fix
How to fix
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
Structured data

Structured data is valid: Organization, WebSite, Article, FAQPage, BreadcrumbList.

Organization, WebSite, Article, FAQPage, BreadcrumbList

5 types: Organization, WebSite, Article, FAQPage, BreadcrumbList

Rich result eligibility

Eligible for rich results via Organization, Article, FAQPage, BreadcrumbList.

Organization, Article, FAQPage, BreadcrumbList

4 types: Organization, Article, FAQPage, BreadcrumbList

Link distribution 63 resources

63 internal and 0 external links.

63 internal, 0 external

63 internal, 0 external

Anchor text

Anchor text describes its destinations.

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Image alt text

All images carry an alt attribute.

Image dimensions

All images declare width and height.

Image formats

No heavy legacy image formats found.

3 already in a modern format

Image loading

Image loading strategy looks sound.

Broken links 25 checked

All 25 checked links resolve.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

1
! Recommended Nothing prevents this page being embedded in a frame, which allows clickjacking.
Content-Security-Policy: frame-ancestors 'self'
quick fix
2
! Recommended A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.
Make the server or the application return a 404 status for unknown addresses. The not-found page can look the same; only the status code has to change.
quick fix
3
! Recommended 3 files have cache lifetimes short enough that returning visitors download 123 KB again.
Serve static assets with a long max-age and a content hash in the filename, so a new version gets a new URL rather than a short expiry.
quick fix
4
! Recommended 3 large images are served at one fixed size, so phones download desktop-sized files.
<img src="hero.jpg" srcset="hero-400.jpg 400w, hero-800.jpg 800w" sizes="(max-width: 600px) 400px, 800px">
moderate
5
· Notice The meta description is 170 characters, so search results will likely cut it short.
quick fix
6
· Notice FAQPage declared without a name or headline.
Give each of these a name, or a headline for an Article. The type says what kind of thing the page is about; without a name it does not say which thing.
quick fix
7
· Notice The other spellings of this address arrive here, but not in one permanent step: a chain costs time on every visit, and a temporary redirect tells search engines the move may not last.
Redirect each spelling straight to the final address with a 301 or 308.
quick fix
8
· Notice theinbetweenself.com has no SPF record, so nothing tells mail servers who may send email as this domain. Spoofed mail is easier, and genuine mail is likelier to land in spam.
Publish a TXT record starting v=spf1 that lists the services that send your mail. A domain that sends none: v=spf1 -all
quick fix
9
· Notice theinbetweenself.com has no DMARC record, so mail servers have no instruction for mail that fails SPF or DKIM. Gmail and Yahoo require one from bulk senders.
Publish a TXT record at _dmarc.theinbetweenself.com, starting with v=DMARC1; p=none; rua=mailto:[email protected] to collect reports, then tighten to quarantine or reject.
quick fix
10
· Notice No Content-Security-Policy, the main defence against cross-site scripting.
Content-Security-Policy: default-src 'self'
involved
11
· Notice No Permissions-Policy header, so any script or embed on the page may ask for the camera, microphone or location.
Permissions-Policy: camera=(), microphone=(), geolocation=()
quick fix
12
· Notice No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
quick fix

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling38 checks · 9 issues
78
On-Page Content & Structure22 checks · 2 issues
97
Core Web Vitals13 checks · 1 issue
96
Schema & Rich Snippets2 checks · 0 issues
100
Media & Links10 checks · 1 issue
96
Overall scoreGrade A · 72/87 passed
90