https://wan4ai.app/
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.
Duplicate title used on 6 pages
Warningduplicates"Blog | Wan 4" is the <title> on 6 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.
Duplicate title used on 7 pages
Warningduplicates"About Wan 4 | Wan 4" 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.
Title too short (24 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (270 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Thin content (277 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Thin content (193 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Thin content (38 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 (61 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Thin content (42 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 (50 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (20 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (22 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (29 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (22 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (47 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 (54 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 (56 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 (46 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 (151 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (12 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (154 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (12 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (143 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (12 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (143 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (12 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (94 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (12 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (36 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 (11 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (38 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 (31 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (10 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Meta description too long (180 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (65 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
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.
Title too short (19 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (134 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (16 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.
Meta description too long (184 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (61 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (174 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Meta description too long (180 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Meta description too long (171 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Thin content (71 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Thin content (123 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 (55 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (26 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Meta description too long (164 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (63 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (164 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (64 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Title too long (66 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (167 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (75 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Meta description too long (178 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (66 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
Thin content (125 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Thin content (144 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 (64 chars)
WarningonPageShort meta descriptions under-use the SERP snippet. Aim for 70–160 characters.
Title too short (21 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Title too short (24 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Meta description too long (173 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too short (22 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (230 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Thin content (227 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (22 chars)
WarningonPageTitles under 30 characters waste SERP real estate and under-use keyword relevance.
Thin content (114 words)
WarningonPagePage has fewer than 300 words of visible text. Thin pages rank poorly and may be flagged as low-quality.
Title too short (12 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.
Meta description too long (166 chars)
WarningonPageMeta descriptions over 160 characters are truncated in the SERP. Tighten the copy.
Title too long (64 chars)
WarningonPageTitles over 60 characters get truncated in search results, hurting click-through rate.
LCP 5.30s (Poor)
CriticalperformanceLargest Contentful Paint on https://wan4ai.app/ is 5.30s. Google targets ≤ 2.5s for a good experience. Slow LCP hurts rankings and bounce rate.
Fix: Optimize the largest above-the-fold element: preload hero images, reduce server response time (TTFB), remove render-blocking resources.
llms.txt does not follow the llmstxt.org structure
InfogeoThe file exists but is missing the conventional header: an H1 (#) with the site name and a blockquote (>) one-line summary. AI tooling that parses llms.txt expects this skeleton to extract a site summary.
Fix: Start the file with `# Site Name` on the first line, then `> One-sentence description of what the site offers.` on the second, followed by your content sections.
Duplicate meta description on 7 pages
Infoduplicates7 pages share the same meta description. Unique descriptions improve CTR and help Google match pages to queries.
Fix: Write a unique meta description per page.
Thin content, eligible for AI generation (38 words)
InfoonPagehttps://wan4ai.app/ja/text-to-video has only 38 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=38
Thin content, eligible for AI generation (42 words)
InfoonPagehttps://wan4ai.app/zh/text-to-video has only 42 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=42
Thin content, eligible for AI generation (47 words)
InfoonPagehttps://wan4ai.app/ja/blog/what-is-wan-4-ja has only 47 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=47
Thin content, eligible for AI generation (56 words)
InfoonPagehttps://wan4ai.app/zh/blog/what-is-wan-4-zh has only 56 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=56
Thin content, eligible for AI generation (143 words)
InfoonPagehttps://wan4ai.app/it/blog has only 143 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=143
Thin content, eligible for AI generation (143 words)
InfoonPagehttps://wan4ai.app/fr/blog has only 143 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=143
Thin content, eligible for AI generation (94 words)
InfoonPagehttps://wan4ai.app/de/blog has only 94 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=94
Thin content, eligible for AI generation (36 words)
InfoonPagehttps://wan4ai.app/ja/blog has only 36 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=36
Thin content, eligible for AI generation (38 words)
InfoonPagehttps://wan4ai.app/zh/blog has only 38 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=38
Thin content, eligible for AI generation (134 words)
InfoonPagehttps://wan4ai.app/zh/about has only 134 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=134
Thin content, eligible for AI generation (71 words)
InfoonPagehttps://wan4ai.app/ja/pricing has only 71 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=71
Thin content, eligible for AI generation (123 words)
InfoonPagehttps://wan4ai.app/zh/pricing has only 123 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=123
Thin content, eligible for AI generation (125 words)
InfoonPagehttps://wan4ai.app/ja has only 125 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=125
Thin content, eligible for AI generation (144 words)
InfoonPagehttps://wan4ai.app/zh has only 144 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=144
Thin content, eligible for AI generation (114 words)
InfoonPagehttps://wan4ai.app/blog has only 114 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=114
URL contains uppercase characters
Infotechnicalhttps://wan4ai.app/pt-BR/blog/what-is-wan-4-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://wan4ai.app/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://wan4ai.app/pt-BR/about 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://wan4ai.app/pt-BR/pricing 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://wan4ai.app/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.
Low structured-data coverage (52% 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 (413 words)
InfoonPagehttps://wan4ai.app/pt-BR/blog/what-is-wan-4-pt-br has only 413 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=413
Thin content, eligible for AI generation (270 words)
InfoonPagehttps://wan4ai.app/it/text-to-video has only 270 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=270
Thin content, eligible for AI generation (277 words)
InfoonPagehttps://wan4ai.app/fr/text-to-video has only 277 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=277
Thin content, eligible for AI generation (193 words)
InfoonPagehttps://wan4ai.app/de/text-to-video has only 193 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=193
Thin content, eligible for AI generation (392 words)
InfoonPagehttps://wan4ai.app/it/blog/what-is-wan-4-it has only 392 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=392
Thin content, eligible for AI generation (415 words)
InfoonPagehttps://wan4ai.app/es/blog/what-is-wan-4-es has only 415 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=415
Thin content, eligible for AI generation (402 words)
InfoonPagehttps://wan4ai.app/fr/blog/what-is-wan-4-fr has only 402 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=402
Thin content, eligible for AI generation (317 words)
InfoonPagehttps://wan4ai.app/de/blog/what-is-wan-4-de has only 317 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=317
Thin content, eligible for AI generation (151 words)
InfoonPagehttps://wan4ai.app/pt-BR/blog has only 151 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=151
Thin content, eligible for AI generation (154 words)
InfoonPagehttps://wan4ai.app/es/blog 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 (374 words)
InfoonPagehttps://wan4ai.app/pt-BR/about has only 374 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=374
Thin content, eligible for AI generation (374 words)
InfoonPagehttps://wan4ai.app/es/about has only 374 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=374
Thin content, eligible for AI generation (374 words)
InfoonPagehttps://wan4ai.app/it/about has only 374 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=374
Thin content, eligible for AI generation (376 words)
InfoonPagehttps://wan4ai.app/fr/about has only 376 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=376
Thin content, eligible for AI generation (374 words)
InfoonPagehttps://wan4ai.app/de/about has only 374 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=374
Thin content, eligible for AI generation (371 words)
InfoonPagehttps://wan4ai.app/ja/about has only 371 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=371
Thin content, eligible for AI generation (338 words)
InfoonPagehttps://wan4ai.app/refund-policy has only 338 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=338
Thin content, eligible for AI generation (230 words)
InfoonPagehttps://wan4ai.app/image-to-video has only 230 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=230
Thin content, eligible for AI generation (227 words)
InfoonPagehttps://wan4ai.app/text-to-video has only 227 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=227
Thin content, eligible for AI generation (350 words)
InfoonPagehttps://wan4ai.app/blog/what-is-wan-4 has only 350 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=350
Thin content, eligible for AI generation (374 words)
InfoonPagehttps://wan4ai.app/about has only 374 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=374