SEO and LLM Optimization Report
For the URLs analyzed on lionpose.com, including both existing content analysis and actionable suggestions.
URL 1: https://lionpose.com/robots.txt
Existing Content Overview
- Restricts access to non-SEO pages (checkout, cart, admin, internal searches, duplicate/filtered URLs).
- Allows indexation of canonical product, collection, and blog pages.
- Sitemap is declared:
Sitemap: https://lionpose.com/sitemap.xml - Defensive blocks for aggressive crawlers and resource protection.
- No explicit "Allow" rules, but not currently needed.
Strengths
- Good coverage of non-useful/duplicate URL blocks.
- Sitemap included for crawler guidance.
- Crawl-delay and targeted rules for problematic bots.
- No canonical content is restricted from indexing.
Potential Weaknesses
- Risk of over-blocking via wildcards.
- No explicit Allow for static resources (
/assets/,/files/), which could affect rendering if custom rules are added. - Some
Disallowrules could accidentally block new/future pages if not routinely reviewed.
Optimized robots.txt Suggestions
- Regularly review
Disallowrules as navigation or category structures evolve. -
Explicitly Allow static asset folders (
/assets/,/files/) if Google Search Console ever reports rendering issues. - Minimize wildcards: Only use patterns like
/*/recommendations/productsif multi-level directories are present.
Replace with more explicit paths if possible. - Extend
crawl-delayto new heavy crawlers if crawl spikes detected. -
Ensure policy pages are blocked only if you don't want them indexed. For example, unblock
/policies/if you want them to rank. - Validate updates in Google robots.txt Tester after each change.
Sample Optimized robots.txt (adapt as needed):
# General robots.txt settings for lionpose.com
User-agent: *
Disallow: /admin
Disallow: /cart
Disallow: /carts
Disallow: /account
Disallow: /orders
Disallow: /checkouts/
Disallow: /checkout
Disallow: /a/downloads/-/*
Disallow: /*?*oseid=*
Disallow: /*preview_theme_id*
Disallow: /*preview_script_id*
Disallow: /collections/*sort_by*
Disallow: /collections/*+*
Disallow: /collections/*%2B*
Disallow: /collections/*%2b*
Disallow: */collections/*filter*
Disallow: /blogs/*+*
Disallow: /blogs/*%2B*
Disallow: /blogs/*%2b*
Disallow: /search
Disallow: /sf_private_access_tokens
Disallow: /.well-known/shopify/monorail
Disallow: /cdn/wpm/*.js
Disallow: /recommendations/products
Disallow: /*/recommendations/products
# Only block /policies/ if you do NOT want it indexed
Disallow: /policies/
Sitemap: https://lionpose.com/sitemap.xml
# Allow static resources if needed
# User-agent: Googlebot
# Allow: /assets/
# Allow: /files/
User-agent: Nutch
Disallow: /
User-agent: AhrefsBot
Crawl-delay: 10
Disallow: (replicate rules above for this bot)
User-agent: MJ12bot
Crawl-delay: 10
User-agent: Pinterest
Crawl-delay: 1
URL 2: https://lionpose.com/llms.txt
Existing Content Overview
- 404 Not Found — No file exists.
- No structured info for LLMs (Large Language Models) or AI agents.
Current Issues
- Missing resource: LLMs, AI crawlers, or parsing agents cannot extract info about LionPose.
Optimization Suggestions
-
Upload/Create llms.txt
Place in the site root as a plain text or markdown file. - Structure for LLMs: Use clear markdown-style headings and sections. Include summary, main features, supported use cases, and contact details.
-
Sample Optimized llms.txt Content:
# LionPose: Human Pose Estimation Platform ## Overview LionPose is a modern platform for real-time 3D human pose estimation. Designed for developers, researchers, and businesses seeking accurate, privacy-focused pose analytics. ## Features - Real-time 3D human pose tracking - Developer SDKs for multiple languages - Privacy-first: On-device processing available - Cross-platform support ## Use Cases - Sports and motion analytics - Virtual fitness and coaching - Rehabilitation and biomechanics research ## Contact Website: https://lionpose.com Email: [email protected] ## Documentation - API Reference: https://lionpose.com/docs - Community Forum: https://lionpose.com/community
-
Best Practices:
- Use plain text or markdown (not HTML or PDF).
- Keep descriptions concise, minimize jargon.
- Link to any docs/resources (publicly accessible).
- Update the file as your product or features change.
Summary Table
| URL | Issue/Status | Existing Content | Optimization Actions |
|---|---|---|---|
| robots.txt | Functional | Good SEO blocking rules | Review for overblocking, add explicit Allow if needed, update wildcards, test changes |
| llms.txt | 404 (Missing) | None | Upload file, use structured markdown, provide SEO/AI-friendly content |
Final Recommendations
- robots.txt: Maintain regularly, update alongside sitemap/structure changes, explicitly allow assets as needed, monitor with GSC or Bing Webmaster Tools.
- llms.txt: Create and upload a clean, structured markdown/plaintext file to improve accessibility and understanding for Large Language Models and AI.
Ready-to-use optimized content for llms.txt is provided above.
For tailored content or additional guidance, update as your details evolve.