SEO report for www.gitbook.com
https://www.gitbook.com/ · checked Mon, 02 Nov 2026 00:09 GMT
Fix these first
- Render-blocking resourceshigh
3 blocking script(s) and 0 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- H1 headingcritical
2 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
- Heading structuremedium
51 headings for 1147 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- 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.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Anchor text qualitymedium
No link text points to two different pages.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- HTML sizemedium
979 kB of HTML – heavy for phones (we only analysed the first 1 MB).
Fix: Remove inline bloat, base64 images and unused markup.
- Imagesmedium
97 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
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 gitbook.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 found at https://www.gitbook.com/sitemap.xml with 347 URLs.
Declared in robots.txt.
This page is listed in it.
No lastmod dates – add accurate ones so search engines know what changed.
- ✓
Canonical URLhigh
Canonical: https://www.gitbook.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://gitbook.io/ → https://www.gitbook.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
gitbook.com redirects to www.gitbook.com.
Search snippet & sharing 88%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“The knowledge layer for AI | GitBook”
About 325px of Google's ~580px desktop width.
- !
Meta descriptionhigh
175 characters, ~1109px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-US"
Content quality 63%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,147 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 64 (plain English), about 8 words per sentence.
- ✓
Topic focushigh
2 of 2 title keywords appear in the main content.
- !
H1 headingcritical
2 H1 headings – one clear H1 is best practice.
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- ✗
Heading structuremedium
51 headings for 1147 words – a lot for the amount of text.
8 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
1% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 59%
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
/llms.txt found.
- ✗
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
Identified as: Organization.
No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).
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 about and contact; missing privacy.
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
1 JSON-LD block(s): Organization, ImageObject, WebSite, Thing, SoftwareApplication.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 75%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
82 internal and 22 external links.
- ✗
Anchor text qualitymedium
No link text points to two different pages.
7 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
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
80 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
979 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 br.
- ✗
Render-blocking resourceshigh
3 blocking script(s) and 0 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- !
Scripts & third partiesmedium
11 script tag(s); files loaded from 5 other domain(s): framerusercontent.com, cdn.amplitude.com, js.hs-scripts.com, googletagmanager.com, events.framer.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
97 image(s).
9 without width/height – can cause layout shift (CLS).
27 image(s) after the first three aren't lazy-loaded.
41 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: public, max-age=0, must-revalidate
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 92%
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=31536000
- ✗
Security headerslow
Present: nosniff.
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 50%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width
- ✗
Image alt textmedium
60 of 97 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✗
Link nameslow
7 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✗
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.