https://story-viewer.online/
Keep your audit and access AI content
Create a free account to generate optimized content from the issues found in this report.
Create my free accountScore by category
Prioritized Action Roadmap
AI-generated plan to improve your score step by step — quick wins first.
No llms.txt file
Infogeo/llms.txt is an emerging convention (llmstxt.org) that helps AI crawlers discover and understand the site structure — a robots.txt for AI. Early adopters report improved visibility in AI-generated answers.
Fix: Create /llms.txt at the domain root: an H1 (#) site name, a one-line blockquote (>) description, then sections linking key pages. Keep it curated — it is a menu, not a sitemap dump.
Duplicate title used on 7 pages
Warningduplicates"Blog - Story Viewer" is the <title> on 7 pages. Each page should have a unique title so search engines (and users) can distinguish them in results.
Fix: Write a unique, descriptive title for each page.
Meta description too long (244 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Thin content (274 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too long (258 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Thin content (295 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too long (258 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Meta description too long (242 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Meta description too long (241 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Meta description too long (256 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Meta description too long (255 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Thin content (249 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (21 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (39 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (22 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (23 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (272 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (295 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (293 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (11 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (38 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (18 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (260 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (42 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (18 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (19 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (27 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (17 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (26 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (29 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (18 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too long (75 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (80 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (83 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (88 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Thin content (269 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too long (74 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (90 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (217 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (104 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (101 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (207 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (92 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (180 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (110 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (166 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (125 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (101 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (92 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too short (58 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Thin content (57 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (48 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Thin content (154 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (37 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Thin content (49 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Meta description too short (32 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (28 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Meta description too long (214 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too short (29 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Meta description too long (235 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content, eligible for AI generation (39 words)
InfoonPagehttps://story-viewer.online/zh-TW/terms has only 39 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=39
Thin content, eligible for AI generation (22 words)
InfoonPagehttps://story-viewer.online/ja/terms has only 22 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=22
Thin content, eligible for AI generation (23 words)
InfoonPagehttps://story-viewer.online/zh/terms has only 23 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=23
Thin content, eligible for AI generation (11 words)
InfoonPagehttps://story-viewer.online/ja/blog has only 11 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=11
Thin content, eligible for AI generation (19 words)
InfoonPagehttps://story-viewer.online/zh/blog has only 19 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=19
Thin content, eligible for AI generation (26 words)
InfoonPagehttps://story-viewer.online/zh-TW/blog has only 26 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=26
Thin content, eligible for AI generation (57 words)
InfoonPagehttps://story-viewer.online/ja has only 57 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=57
Thin content, eligible for AI generation (49 words)
InfoonPagehttps://story-viewer.online/zh has only 49 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=49
CLS 0.131 (Needs improvement)
WarningperformanceCumulative Layout Shift on https://story-viewer.online/ is 0.131. Target ≤ 0.1. Layout shifts frustrate users (misclicks) and are a ranking factor.
Fix: Set width/height on images and ads, avoid injecting content above existing elements, use CSS aspect-ratio.
URL contains uppercase characters
Infotechnicalhttps://story-viewer.online/pt-BR/terms has uppercase characters in its path. Google treats URLs as case-sensitive. Mixing cases can lead to duplicate content issues.
Fix: Force lowercase for all URLs and use 301 redirects from uppercase variants to the lowercase URL.
URL contains uppercase characters
Infotechnicalhttps://story-viewer.online/zh-TW/terms has uppercase characters in its path. Google treats URLs as case-sensitive. Mixing cases can lead to duplicate content issues.
Fix: Force lowercase for all URLs and use 301 redirects from uppercase variants to the lowercase URL.
URL contains uppercase characters
Infotechnicalhttps://story-viewer.online/pt-BR/blog has uppercase characters in its path. Google treats URLs as case-sensitive. Mixing cases can lead to duplicate content issues.
Fix: Force lowercase for all URLs and use 301 redirects from uppercase variants to the lowercase URL.
URL contains uppercase characters
Infotechnicalhttps://story-viewer.online/zh-TW/blog has uppercase characters in its path. Google treats URLs as case-sensitive. Mixing cases can lead to duplicate content issues.
Fix: Force lowercase for all URLs and use 301 redirects from uppercase variants to the lowercase URL.
URL contains uppercase characters
Infotechnicalhttps://story-viewer.online/pt-BR has uppercase characters in its path. Google treats URLs as case-sensitive. Mixing cases can lead to duplicate content issues.
Fix: Force lowercase for all URLs and use 301 redirects from uppercase variants to the lowercase URL.
URL contains uppercase characters
Infotechnicalhttps://story-viewer.online/zh-TW has uppercase characters in its path. Google treats URLs as case-sensitive. Mixing cases can lead to duplicate content issues.
Fix: Force lowercase for all URLs and use 301 redirects from uppercase variants to the lowercase URL.
Low structured-data coverage (100% of pages have no JSON-LD)
InfogeoMost indexable pages carry no JSON-LD entities. Answer engines use structured data to identify and ground entities (organization, products, FAQs) when composing citations — bare pages rely on raw text inference only.
Fix: Add at least Organization/WebSite JSON-LD site-wide and the most specific type per template (Article, Product, FAQPage). BACKR’s schema checker lists the exact pages without structured data.
Thin content, eligible for AI generation (320 words)
InfoonPagehttps://story-viewer.online/id/terms has only 320 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=320
Thin content, eligible for AI generation (274 words)
InfoonPagehttps://story-viewer.online/tr/terms has only 274 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=274
Thin content, eligible for AI generation (295 words)
InfoonPagehttps://story-viewer.online/ru/terms has only 295 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=295
Thin content, eligible for AI generation (365 words)
InfoonPagehttps://story-viewer.online/fr/terms has only 365 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=365
Thin content, eligible for AI generation (357 words)
InfoonPagehttps://story-viewer.online/pt-BR/terms has only 357 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=357
Thin content, eligible for AI generation (360 words)
InfoonPagehttps://story-viewer.online/es/terms has only 360 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=360
Thin content, eligible for AI generation (308 words)
InfoonPagehttps://story-viewer.online/de/terms has only 308 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=308
Thin content, eligible for AI generation (249 words)
InfoonPagehttps://story-viewer.online/ko/terms has only 249 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=249
Thin content, eligible for AI generation (272 words)
InfoonPagehttps://story-viewer.online/tr/blog has only 272 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=272
Thin content, eligible for AI generation (295 words)
InfoonPagehttps://story-viewer.online/id/blog has only 295 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=295
Thin content, eligible for AI generation (347 words)
InfoonPagehttps://story-viewer.online/fr/blog has only 347 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=347
Thin content, eligible for AI generation (293 words)
InfoonPagehttps://story-viewer.online/ru/blog has only 293 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=293
Thin content, eligible for AI generation (357 words)
InfoonPagehttps://story-viewer.online/pt-BR/blog has only 357 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=357
Thin content, eligible for AI generation (353 words)
InfoonPagehttps://story-viewer.online/es/blog has only 353 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=353
Thin content, eligible for AI generation (302 words)
InfoonPagehttps://story-viewer.online/de/blog has only 302 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=302
Thin content, eligible for AI generation (260 words)
InfoonPagehttps://story-viewer.online/ko/blog has only 260 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=260
Thin content, eligible for AI generation (315 words)
InfoonPagehttps://story-viewer.online/blog/view-tiktok-stories-on-pc has only 315 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=315
Thin content, eligible for AI generation (375 words)
InfoonPagehttps://story-viewer.online/blog/tiktok-story-viewer-complete-guide has only 375 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=375
Thin content, eligible for AI generation (334 words)
InfoonPagehttps://story-viewer.online/blog/can-you-see-who-views-your-tiktok-story has only 334 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=334
Thin content, eligible for AI generation (342 words)
InfoonPagehttps://story-viewer.online/blog/download-tiktok-stories has only 342 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=342
Thin content, eligible for AI generation (269 words)
InfoonPagehttps://story-viewer.online/blog/best-tiktok-story-viewers has only 269 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=269
Thin content, eligible for AI generation (440 words)
InfoonPagehttps://story-viewer.online/blog/anonymous-tiktok-story-viewer has only 440 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=440
Thin content, eligible for AI generation (154 words)
InfoonPagehttps://story-viewer.online/zh-TW has only 154 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=154
Thin content, eligible for AI generation (305 words)
InfoonPagehttps://story-viewer.online/privacy has only 305 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=305
Thin content, eligible for AI generation (443 words)
InfoonPagehttps://story-viewer.online/terms has only 443 words of visible text. This page is a good candidate for BACKR's content engine — generate an optimized, ~700-word version from an SEO brief.
Fix: [content-engine] target=700 source=443