npm - @rankcli/agent-runtime - Versions diffs - 0.0.15 → 0.0.16 - Mend

@rankcli/agent-runtime 0.0.15 → 0.0.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (202) hide show

package/dist/index.d.mts +43 -393
package/dist/index.d.ts +43 -393
package/dist/index.js +306 -6526
package/dist/index.mjs +202 -6412
package/package.json +6 -1
package/scripts/build-deno.ts +0 -134
package/src/analyzers/core-web-vitals-analyzer.test.ts +0 -236
package/src/analyzers/core-web-vitals-analyzer.ts +0 -557
package/src/analyzers/geo-analyzer.test.ts +0 -310
package/src/analyzers/geo-analyzer.ts +0 -814
package/src/analyzers/image-optimization-analyzer.test.ts +0 -145
package/src/analyzers/image-optimization-analyzer.ts +0 -348
package/src/analyzers/index.ts +0 -233
package/src/analyzers/internal-linking-analyzer.test.ts +0 -141
package/src/analyzers/internal-linking-analyzer.ts +0 -419
package/src/analyzers/mobile-seo-analyzer.test.ts +0 -140
package/src/analyzers/mobile-seo-analyzer.ts +0 -455
package/src/analyzers/security-headers-analyzer.test.ts +0 -115
package/src/analyzers/security-headers-analyzer.ts +0 -318
package/src/analyzers/structured-data-analyzer.test.ts +0 -210
package/src/analyzers/structured-data-analyzer.ts +0 -590
package/src/audit/ai/analyzer.ts +0 -347
package/src/audit/ai/index.ts +0 -29
package/src/audit/ai/prompts/content-analysis.ts +0 -271
package/src/audit/ai/types.ts +0 -179
package/src/audit/checks/additional-checks.ts +0 -439
package/src/audit/checks/agent-experience.ts +0 -108
package/src/audit/checks/ai-citation-worthiness.ts +0 -399
package/src/audit/checks/ai-content-structure.ts +0 -325
package/src/audit/checks/ai-readiness.ts +0 -406
package/src/audit/checks/anchor-text.ts +0 -179
package/src/audit/checks/answer-conciseness.ts +0 -322
package/src/audit/checks/asset-minification.ts +0 -270
package/src/audit/checks/bing-optimization.ts +0 -206
package/src/audit/checks/brand-mention-optimization.ts +0 -349
package/src/audit/checks/caching-headers.ts +0 -305
package/src/audit/checks/canonical-advanced.ts +0 -150
package/src/audit/checks/canonical-domain.ts +0 -196
package/src/audit/checks/citation-quality.ts +0 -358
package/src/audit/checks/client-rendering.ts +0 -542
package/src/audit/checks/color-contrast.ts +0 -342
package/src/audit/checks/content-freshness.ts +0 -170
package/src/audit/checks/content-science.ts +0 -589
package/src/audit/checks/conversion-elements.ts +0 -526
package/src/audit/checks/crawlability.ts +0 -220
package/src/audit/checks/directory-listing.ts +0 -172
package/src/audit/checks/dom-analysis.ts +0 -191
package/src/audit/checks/dom-size.ts +0 -246
package/src/audit/checks/duplicate-content.ts +0 -194
package/src/audit/checks/eeat-signals.ts +0 -990
package/src/audit/checks/entity-seo.ts +0 -396
package/src/audit/checks/featured-snippet.ts +0 -473
package/src/audit/checks/freshness-signals.ts +0 -443
package/src/audit/checks/funnel-intent.ts +0 -463
package/src/audit/checks/hreflang.ts +0 -174
package/src/audit/checks/html-compliance.ts +0 -302
package/src/audit/checks/image-dimensions.ts +0 -167
package/src/audit/checks/images.ts +0 -160
package/src/audit/checks/indexnow.ts +0 -275
package/src/audit/checks/interactive-tools.ts +0 -475
package/src/audit/checks/internal-link-graph.ts +0 -436
package/src/audit/checks/keyword-analysis.ts +0 -239
package/src/audit/checks/keyword-cannibalization.ts +0 -385
package/src/audit/checks/keyword-placement.ts +0 -471
package/src/audit/checks/links.ts +0 -273
package/src/audit/checks/llms-txt.ts +0 -224
package/src/audit/checks/local-seo.ts +0 -296
package/src/audit/checks/mobile.ts +0 -167
package/src/audit/checks/modern-images.ts +0 -226
package/src/audit/checks/navboost-signals.ts +0 -395
package/src/audit/checks/on-page.ts +0 -209
package/src/audit/checks/page-resources.ts +0 -285
package/src/audit/checks/pagination.ts +0 -180
package/src/audit/checks/performance.ts +0 -153
package/src/audit/checks/platform-presence.ts +0 -580
package/src/audit/checks/rag-chunk-readiness.test.ts +0 -159
package/src/audit/checks/rag-chunk-readiness.ts +0 -163
package/src/audit/checks/redirect-analysis.ts +0 -153
package/src/audit/checks/redirect-chain.ts +0 -389
package/src/audit/checks/resource-hints.ts +0 -420
package/src/audit/checks/responsive-css.ts +0 -247
package/src/audit/checks/responsive-images.ts +0 -396
package/src/audit/checks/review-ecosystem.ts +0 -415
package/src/audit/checks/robots-validation.ts +0 -373
package/src/audit/checks/security-headers.ts +0 -188
package/src/audit/checks/security.ts +0 -144
package/src/audit/checks/serp-preview.ts +0 -251
package/src/audit/checks/site-maturity.ts +0 -453
package/src/audit/checks/social-meta.test.ts +0 -275
package/src/audit/checks/social-meta.ts +0 -134
package/src/audit/checks/soft-404.ts +0 -151
package/src/audit/checks/structured-data.ts +0 -238
package/src/audit/checks/tech-detection.ts +0 -496
package/src/audit/checks/topical-clusters.ts +0 -435
package/src/audit/checks/tracker-bloat.ts +0 -462
package/src/audit/checks/tracking-verification.test.ts +0 -371
package/src/audit/checks/tracking-verification.ts +0 -636
package/src/audit/checks/url-safety.ts +0 -682
package/src/audit/deno-entry.ts +0 -66
package/src/audit/discovery/index.ts +0 -15
package/src/audit/discovery/link-crawler.ts +0 -233
package/src/audit/discovery/repo-routes.ts +0 -347
package/src/audit/engine.ts +0 -633
package/src/audit/fixes/index.ts +0 -209
package/src/audit/fixes/social-meta-fixes.test.ts +0 -329
package/src/audit/fixes/social-meta-fixes.ts +0 -463
package/src/audit/index.ts +0 -74
package/src/audit/runner.test.ts +0 -299
package/src/audit/runner.ts +0 -130
package/src/audit/types.ts +0 -1987
package/src/content/featured-snippet.ts +0 -367
package/src/content/generator.test.ts +0 -534
package/src/content/generator.ts +0 -501
package/src/content/headline.ts +0 -317
package/src/content/index.ts +0 -62
package/src/content/intent.ts +0 -258
package/src/content/keyword-density.ts +0 -349
package/src/content/readability.ts +0 -262
package/src/executor.ts +0 -336
package/src/fixer/framework-fixes.test.ts +0 -489
package/src/fixer/framework-fixes.ts +0 -5287
package/src/fixer/index.ts +0 -6
package/src/fixer/schemas.ts +0 -971
package/src/fixer.ts +0 -642
package/src/frameworks/detector.test.ts +0 -248
package/src/frameworks/detector.ts +0 -899
package/src/frameworks/index.ts +0 -68
package/src/frameworks/recipes/angular.yaml +0 -171
package/src/frameworks/recipes/astro.yaml +0 -206
package/src/frameworks/recipes/django.yaml +0 -180
package/src/frameworks/recipes/laravel.yaml +0 -137
package/src/frameworks/recipes/nextjs.yaml +0 -268
package/src/frameworks/recipes/nuxt.yaml +0 -175
package/src/frameworks/recipes/rails.yaml +0 -188
package/src/frameworks/recipes/react.yaml +0 -202
package/src/frameworks/recipes/sveltekit.yaml +0 -154
package/src/frameworks/recipes/vue.yaml +0 -137
package/src/frameworks/recipes/wordpress.yaml +0 -209
package/src/frameworks/suggestion-engine.ts +0 -357
package/src/geo/geo-content.test.ts +0 -305
package/src/geo/geo-content.ts +0 -266
package/src/geo/geo-history.test.ts +0 -473
package/src/geo/geo-history.ts +0 -433
package/src/geo/geo-tracker.test.ts +0 -359
package/src/geo/geo-tracker.ts +0 -411
package/src/geo/index.ts +0 -11
package/src/geo/llm-citation-checker.ts +0 -188
package/src/git/commit-helper.test.ts +0 -261
package/src/git/commit-helper.ts +0 -329
package/src/git/index.ts +0 -12
package/src/git/pr-helper.test.ts +0 -284
package/src/git/pr-helper.ts +0 -307
package/src/index.ts +0 -76
package/src/keywords/ai-keyword-engine.ts +0 -1062
package/src/keywords/ai-summarizer.ts +0 -387
package/src/keywords/ci-mode.ts +0 -555
package/src/keywords/engine.ts +0 -359
package/src/keywords/index.ts +0 -151
package/src/keywords/llm-judge.ts +0 -357
package/src/keywords/nlp-analysis.ts +0 -706
package/src/keywords/prioritizer.ts +0 -295
package/src/keywords/site-crawler.ts +0 -342
package/src/keywords/sources/autocomplete.ts +0 -139
package/src/keywords/sources/competitive-search.ts +0 -450
package/src/keywords/sources/competitor-analysis.ts +0 -374
package/src/keywords/sources/dataforseo.ts +0 -206
package/src/keywords/sources/free-sources.ts +0 -294
package/src/keywords/sources/gsc.ts +0 -123
package/src/keywords/topic-grouping.ts +0 -327
package/src/keywords/types.ts +0 -144
package/src/keywords/wizard.ts +0 -457
package/src/loader.ts +0 -40
package/src/ranking/index.ts +0 -5
package/src/ranking/serp-client.ts +0 -348
package/src/ranking/tracker.ts +0 -380
package/src/ranking/types.ts +0 -123
package/src/reports/index.ts +0 -7
package/src/reports/report-generator.test.ts +0 -293
package/src/reports/report-generator.ts +0 -713
package/src/scheduler/alerts.test.ts +0 -458
package/src/scheduler/alerts.ts +0 -328
package/src/scheduler/index.ts +0 -8
package/src/scheduler/scheduled-audit.test.ts +0 -377
package/src/scheduler/scheduled-audit.ts +0 -149
package/src/test/integration-test.ts +0 -325
package/src/tools/analyzer.ts +0 -373
package/src/tools/crawl.ts +0 -293
package/src/tools/files.ts +0 -301
package/src/tools/h1-fixer.ts +0 -249
package/src/tools/index.ts +0 -67
package/src/tracking/github-action.ts +0 -326
package/src/tracking/google-analytics.ts +0 -265
package/src/tracking/index.ts +0 -45
package/src/tracking/report-generator.ts +0 -386
package/src/tracking/search-console.ts +0 -335
package/src/types.ts +0 -148
package/src/utils/http.ts +0 -302
package/src/wasm-adapter.ts +0 -297
package/src/wasm-entry.ts +0 -14
package/tsconfig.json +0 -17
package/tsup.wasm.config.ts +0 -26
package/vitest.config.ts +0 -15

package/src/frameworks/recipes/rails.yaml DELETED Viewed

@@ -1,188 +0,0 @@
-# Ruby on Rails SEO Recipe
-# Rails is server-rendered by default, excellent for SEO
-framework: rails
-display_name: Ruby on Rails
-category: server-rendered
-ssr_default: true
-seo_strengths:
-  - "Server-rendered HTML by default"
-  - "Turbo for fast navigation without SPA"
-  - "Strong conventions reduce mistakes"
-  - "Mature gem ecosystem"
-checks:
-  - code: RAILS_NO_META_TAGS_GEM
-    severity: warning
-    title: "Not using meta-tags gem"
-    description: "The meta-tags gem provides a clean API for SEO tags."
-    howToFix: |
-      Add meta-tags to Gemfile:
-      ```ruby
-      gem 'meta-tags'
-      ```
-      Run `bundle install`, then:
-      ```ruby
-      # app/views/layouts/application.html.erb
-      <head>
-        <%= display_meta_tags site: 'Your Site' %>
-      </head>
-      ```
-      ```ruby
-      # In controllers or views
-      set_meta_tags title: 'Page Title',
-                    description: 'Page description',
-                    keywords: 'seo, rails'
-      ```
-  - code: RAILS_NO_SITEMAP_GEM
-    severity: warning
-    title: "Not using sitemap_generator gem"
-    description: "sitemap_generator creates SEO-friendly sitemaps automatically."
-    howToFix: |
-      Add to Gemfile:
-      ```ruby
-      gem 'sitemap_generator'
-      ```
-      Generate config:
-      ```bash
-      rails sitemap:install
-      ```
-      Configure config/sitemap.rb:
-      ```ruby
-      SitemapGenerator::Sitemap.default_host = "https://yoursite.com"
-      SitemapGenerator::Sitemap.create do
-        add '/about', changefreq: 'monthly'
-        Product.find_each do |product|
-          add product_path(product), lastmod: product.updated_at
-        end
-      end
-      ```
-      Generate: `rails sitemap:refresh`
-  - code: RAILS_NO_CANONICAL
-    severity: warning
-    title: "Missing canonical URLs"
-    description: "Rails apps with multiple URLs for same content need canonicals."
-    howToFix: |
-      Add canonical tag in layout:
-      ```erb
-      <!-- Using meta-tags gem -->
-      <%= display_meta_tags canonical: request.original_url %>
-      <!-- Or manually -->
-      <link rel="canonical" href="<%= request.original_url.split('?').first %>" />
-      ```
-  - code: RAILS_TURBO_BREAKS_CRAWLERS
-    severity: notice
-    title: "Turbo may affect JavaScript-dependent crawlers"
-    description: "Turbo Drive updates pages via JavaScript, which some crawlers may miss."
-    howToFix: |
-      For SEO-critical pages, ensure content is in initial HTML.
-      For dynamic content, add data-turbo="false":
-      ```erb
-      <%= link_to 'Critical Page', critical_path, data: { turbo: false } %>
-      ```
-      Or disable for specific pages:
-      ```erb
-      <meta name="turbo-visit-control" content="reload">
-      ```
-  - code: RAILS_NO_JSON_LD
-    severity: notice
-    title: "No structured data detected"
-    description: "Add JSON-LD for rich snippets."
-    howToFix: |
-      Create a helper:
-      ```ruby
-      # app/helpers/seo_helper.rb
-      module SeoHelper
-        def json_ld(data)
-          content_tag :script, data.to_json.html_safe,
-                      type: 'application/ld+json'
-        end
-      end
-      ```
-      Use in views:
-      ```erb
-      <%= json_ld({
-        "@context" => "https://schema.org",
-        "@type" => "Product",
-        "name" => @product.name,
-        "description" => @product.description
-      }) %>
-      ```
-  - code: RAILS_SLOW_QUERIES
-    severity: warning
-    title: "N+1 queries may slow pages"
-    description: "Slow pages hurt SEO. Use includes/eager_load."
-    howToFix: |
-      Use bullet gem to detect N+1:
-      ```ruby
-      # Gemfile
-      gem 'bullet', group: 'development'
-      ```
-      Fix with includes:
-      ```ruby
-      # Before (N+1)
-      @posts = Post.all
-      @posts.each { |p| p.author.name }
-      # After (2 queries)
-      @posts = Post.includes(:author).all
-      ```
-  - code: RAILS_NO_CACHING
-    severity: notice
-    title: "Page caching not configured"
-    description: "Rails caching can dramatically improve response times."
-    howToFix: |
-      Enable caching in production:
-      ```ruby
-      # config/environments/production.rb
-      config.action_controller.perform_caching = true
-      config.cache_store = :redis_cache_store, { url: ENV['REDIS_URL'] }
-      ```
-      Use fragment caching:
-      ```erb
-      <% cache @product do %>
-        <%= render @product %>
-      <% end %>
-      ```
-performance_tips:
-  - "Use Russian doll caching for nested views"
-  - "Enable asset fingerprinting and CDN"
-  - "Use Turbo for SPA-like experience"
-  - "Profile with rack-mini-profiler"
-  - "Use Postgres for full-text search instead of LIKE"
-recommended_gems:
-  seo:
-    - "meta-tags - SEO tag management"
-    - "sitemap_generator - XML sitemaps"
-  performance:
-    - "bullet - N+1 detection"
-    - "rack-mini-profiler - Performance profiling"
-    - "bootsnap - Faster boot times"

package/src/frameworks/recipes/react.yaml DELETED Viewed

@@ -1,202 +0,0 @@
-# React SEO Recipe
-# Client-side rendering frameworks are notoriously problematic for SEO
-framework: react
-display_name: React
-category: spa
-ssr_default: false
-seo_challenges:
-  - "Client-side rendering means empty HTML for crawlers"
-  - "Dynamic content invisible to search engines"
-  - "Slow First Contentful Paint"
-  - "No server-side meta tag generation"
-  - "JavaScript-dependent routing breaks crawlability"
-checks:
-  # Critical - these will severely hurt SEO
-  - code: REACT_CSR_DETECTED
-    severity: error
-    title: "Client-side rendered React app detected"
-    description: "React apps without SSR send empty HTML to crawlers. Search engines may not index your content."
-    impact: "Critical - your content is likely invisible to Google"
-    howToFix: |
-      Option 1: Migrate to Next.js for automatic SSR/SSG
-      Option 2: Add prerendering with react-snap or prerender.io
-      Option 3: Use react-helmet-async with a prerender service
-    detection:
-      html_patterns:
-        - '<div id="root"></div>'
-        - '<div id="app"></div>'
-      missing_content: true  # Body has minimal text content
-  - code: REACT_NO_SSR_META
-    severity: error
-    title: "Meta tags not server-rendered"
-    description: "Title and meta description are set client-side and won't be seen by crawlers."
-    impact: "Search results will show wrong or missing title/description"
-    howToFix: |
-      For Vite/CRA: Use a prerender plugin or migrate to Next.js
-      Quick fix with vite-plugin-ssr:
-      ```tsx
-      // pages/+Head.tsx
-      export function Head() {
-        return <>
-          <title>Your Title</title>
-          <meta name="description" content="Your description" />
-        </>
-      }
-      ```
-    detection:
-      title_in_js: true
-      title_not_in_html: true
-  - code: REACT_HYDRATION_MISMATCH
-    severity: warning
-    title: "Hydration mismatch detected"
-    description: "Server HTML differs from client render, causing flicker and potential SEO issues."
-    impact: "Can cause content to briefly disappear, confusing crawlers"
-    howToFix: |
-      Common causes:
-      1. Using Date.now() or Math.random() in render
-      2. Browser-only APIs like window.localStorage
-      3. Different data on server vs client
-      Fix: Use useEffect for browser-only code:
-      ```tsx
-      const [mounted, setMounted] = useState(false);
-      useEffect(() => setMounted(true), []);
-      if (!mounted) return null; // or skeleton
-      ```
-  # Warnings - important but not critical
-  - code: REACT_HELMET_NOT_ASYNC
-    severity: warning
-    title: "Using react-helmet instead of react-helmet-async"
-    description: "react-helmet has memory leaks and doesn't work properly with SSR."
-    howToFix: |
-      Replace react-helmet with react-helmet-async:
-      ```bash
-      npm uninstall react-helmet
-      npm install react-helmet-async
-      ```
-      Update imports:
-      ```tsx
-      // Before
-      import { Helmet } from 'react-helmet';
-      // After
-      import { Helmet, HelmetProvider } from 'react-helmet-async';
-      // Wrap app in provider
-      <HelmetProvider>
-        <App />
-      </HelmetProvider>
-      ```
-  - code: REACT_ROUTER_NO_SSR
-    severity: warning
-    title: "React Router without server-side support"
-    description: "Client-side routing breaks when crawlers access URLs directly."
-    howToFix: |
-      Ensure your server returns the same HTML for all routes.
-      For static hosting (Netlify, Vercel):
-      Add a redirect rule to serve index.html for all routes.
-      netlify.toml:
-      ```toml
-      [[redirects]]
-        from = "/*"
-        to = "/index.html"
-        status = 200
-      ```
-  - code: REACT_NO_PRERENDER
-    severity: warning
-    title: "No prerendering configured"
-    description: "Static pages could be prerendered for better SEO and performance."
-    howToFix: |
-      Add react-snap for build-time prerendering:
-      ```bash
-      npm install react-snap
-      ```
-      package.json:
-      ```json
-      {
-        "scripts": {
-          "postbuild": "react-snap"
-        },
-        "reactSnap": {
-          "source": "build"
-        }
-      }
-      ```
-  # Performance-related
-  - code: REACT_BUNDLE_TOO_LARGE
-    severity: warning
-    title: "React bundle too large"
-    description: "Large JavaScript bundles delay interactivity and hurt Core Web Vitals."
-    howToFix: |
-      1. Use React.lazy() for code splitting:
-      ```tsx
-      const HeavyComponent = React.lazy(() => import('./HeavyComponent'));
-      <Suspense fallback={<Loading />}>
-        <HeavyComponent />
-      </Suspense>
-      ```
-      2. Analyze bundle with source-map-explorer:
-      ```bash
-      npm install source-map-explorer
-      npx source-map-explorer build/static/js/*.js
-      ```
-  - code: REACT_NO_SUSPENSE
-    severity: notice
-    title: "Not using Suspense for data fetching"
-    description: "Without Suspense, content pops in causing layout shifts (CLS)."
-    howToFix: |
-      Use Suspense with a data fetching library:
-      ```tsx
-      <Suspense fallback={<Skeleton />}>
-        <DataComponent />
-      </Suspense>
-      ```
-performance_tips:
-  - "Use React.memo() for expensive components"
-  - "Lazy load routes with React.lazy()"
-  - "Use useMemo/useCallback to prevent unnecessary rerenders"
-  - "Consider using Preact for smaller bundle size"
-  - "Use production builds (NODE_ENV=production)"
-migration_paths:
-  nextjs:
-    effort: medium
-    benefits:
-      - "Automatic SSR/SSG"
-      - "Built-in Image optimization"
-      - "File-based routing"
-      - "API routes"
-    guide: "https://nextjs.org/docs/migrating/from-create-react-app"
-  remix:
-    effort: medium
-    benefits:
-      - "Nested routing with data loading"
-      - "Progressive enhancement"
-      - "Better error boundaries"
-    guide: "https://remix.run/docs/en/main/guides/migrating-react-router-app"
-  vite-ssr:
-    effort: low
-    benefits:
-      - "Keep existing code"
-      - "Add SSR incrementally"
-    guide: "https://vite-plugin-ssr.com/"

package/src/frameworks/recipes/sveltekit.yaml DELETED Viewed

@@ -1,154 +0,0 @@
-# SvelteKit SEO Recipe
-# SvelteKit has excellent SSR and SSG support with minimal overhead
-framework: sveltekit
-display_name: SvelteKit
-category: meta-framework
-base_framework: svelte
-ssr_default: true
-seo_strengths:
-  - "SSR by default"
-  - "Excellent performance (small runtime)"
-  - "Built-in prerendering"
-  - "File-based routing"
-  - "Form actions for progressive enhancement"
-checks:
-  - code: SVELTEKIT_NO_LOAD_FUNCTION
-    severity: warning
-    title: "Page without load function"
-    description: "Data fetching in +page.svelte bypasses SSR. Use +page.server.ts or +page.ts."
-    howToFix: |
-      Move data fetching to a load function:
-      ```ts
-      // src/routes/products/+page.server.ts
-      export async function load({ fetch }) {
-        const products = await fetch('/api/products').then(r => r.json());
-        return { products };
-      }
-      ```
-      ```svelte
-      <!-- src/routes/products/+page.svelte -->
-      <script>
-        export let data;
-      </script>
-      {#each data.products as product}
-        <div>{product.name}</div>
-      {/each}
-      ```
-  - code: SVELTEKIT_NO_LAYOUT_HEAD
-    severity: warning
-    title: "Missing svelte:head in layout"
-    description: "Common meta tags should be in a layout for consistency."
-    howToFix: |
-      Add svelte:head to your layout:
-      ```svelte
-      <!-- src/routes/+layout.svelte -->
-      <script>
-        import { page } from '$app/stores';
-      </script>
-      <svelte:head>
-        <title>{$page.data.title ?? 'Your Site'}</title>
-        <meta name="description" content={$page.data.description ?? 'Default description'} />
-        <link rel="canonical" href={$page.url.href} />
-      </svelte:head>
-      <slot />
-      ```
-  - code: SVELTEKIT_NO_PRERENDER
-    severity: notice
-    title: "Static pages not prerendered"
-    description: "Static pages should be prerendered for best performance."
-    howToFix: |
-      Add prerender to static pages:
-      ```ts
-      // src/routes/about/+page.ts
-      export const prerender = true;
-      ```
-      Or set default in svelte.config.js:
-      ```js
-      kit: {
-        prerender: {
-          default: true
-        }
-      }
-      ```
-  - code: SVELTEKIT_NO_TRAILING_SLASH
-    severity: notice
-    title: "Inconsistent trailing slash handling"
-    description: "Configure trailing slash to avoid duplicate content."
-    howToFix: |
-      Set in svelte.config.js:
-      ```js
-      kit: {
-        trailingSlash: 'never' // or 'always'
-      }
-      ```
-  - code: SVELTEKIT_ENHANCED_IMAGE
-    severity: notice
-    title: "Not using enhanced images"
-    description: "SvelteKit supports enhanced images with @sveltejs/enhanced-img."
-    howToFix: |
-      Install enhanced images:
-      ```bash
-      npm install @sveltejs/enhanced-img
-      ```
-      ```svelte
-      <script>
-        import { Image } from '@sveltejs/enhanced-img';
-        import heroImage from '$lib/images/hero.jpg';
-      </script>
-      <Image src={heroImage} alt="Hero" />
-      ```
-  - code: SVELTEKIT_NO_SITEMAP
-    severity: warning
-    title: "Missing sitemap"
-    description: "Use svelte-sitemap or generate manually."
-    howToFix: |
-      Option 1: Use svelte-sitemap
-      ```bash
-      npm install svelte-sitemap
-      npx svelte-sitemap --domain https://yoursite.com
-      ```
-      Option 2: Create src/routes/sitemap.xml/+server.ts:
-      ```ts
-      export async function GET() {
-        const pages = ['/', '/about', '/products'];
-        const sitemap = `<?xml version="1.0" encoding="UTF-8"?>
-          <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
-            ${pages.map(page => `
-              <url>
-                <loc>https://yoursite.com${page}</loc>
-              </url>
-            `).join('')}
-          </urlset>`;
-        return new Response(sitemap, {
-          headers: { 'Content-Type': 'application/xml' }
-        });
-      }
-      ```
-performance_tips:
-  - "Use load functions for SSR data"
-  - "Prerender static pages"
-  - "Use streaming for slow data sources"
-  - "Leverage Svelte's small runtime"
-  - "Use form actions for progressive enhancement"

package/src/frameworks/recipes/vue.yaml DELETED Viewed

@@ -1,137 +0,0 @@
-# Vue.js SEO Recipe
-# Similar challenges to React for client-side rendered apps
-framework: vue
-display_name: Vue.js
-category: spa
-ssr_default: false
-seo_challenges:
-  - "Client-side rendering sends empty HTML to crawlers"
-  - "Vue Router requires proper server configuration"
-  - "Async components delay content rendering"
-  - "No built-in meta tag management"
-checks:
-  - code: VUE_CSR_DETECTED
-    severity: error
-    title: "Client-side rendered Vue app detected"
-    description: "Vue apps without SSR send empty HTML to crawlers."
-    impact: "Your content may not be indexed by search engines"
-    howToFix: |
-      Option 1: Migrate to Nuxt for automatic SSR/SSG
-      Option 2: Add SSR with @vue/server-renderer
-      Option 3: Use prerendering with prerender-spa-plugin
-      For Nuxt migration, most Vue components work directly.
-  - code: VUE_NO_META_MANAGEMENT
-    severity: error
-    title: "No meta tag management library"
-    description: "Title and meta description are not dynamically managed."
-    howToFix: |
-      Install @vueuse/head or vue-meta:
-      ```bash
-      npm install @vueuse/head
-      ```
-      ```ts
-      // main.ts
-      import { createHead } from '@vueuse/head';
-      const head = createHead();
-      app.use(head);
-      ```
-      ```vue
-      <script setup>
-      import { useHead } from '@vueuse/head';
-      useHead({
-        title: 'Page Title',
-        meta: [
-          { name: 'description', content: 'Page description' },
-        ],
-      });
-      </script>
-      ```
-  - code: VUE_ROUTER_HISTORY_MODE
-    severity: warning
-    title: "Vue Router not in history mode"
-    description: "Hash mode (#/) creates ugly URLs and SEO issues."
-    howToFix: |
-      Use createWebHistory instead of createWebHashHistory:
-      ```ts
-      import { createRouter, createWebHistory } from 'vue-router';
-      const router = createRouter({
-        history: createWebHistory(),
-        routes: [...],
-      });
-      ```
-      Then configure your server to return index.html for all routes.
-  - code: VUE_ASYNC_COMPONENT_NO_LOADING
-    severity: warning
-    title: "Async components without loading state"
-    description: "Async components can cause CLS when they pop in."
-    howToFix: |
-      Provide a loading component:
-      ```ts
-      import { defineAsyncComponent } from 'vue';
-      const AsyncComp = defineAsyncComponent({
-        loader: () => import('./HeavyComponent.vue'),
-        loadingComponent: LoadingSpinner,
-        delay: 200,
-      });
-      ```
-  - code: VUE_NO_KEY_ON_LIST
-    severity: notice
-    title: "v-for without :key attribute"
-    description: "Missing keys can cause rendering issues and affect SEO crawling."
-    howToFix: |
-      Always use :key with v-for:
-      ```vue
-      <div v-for="item in items" :key="item.id">
-        {{ item.name }}
-      </div>
-      ```
-  - code: VUE_TRANSITION_CLS
-    severity: notice
-    title: "Transitions may cause layout shifts"
-    description: "CSS transitions that change element size cause CLS."
-    howToFix: |
-      Use transform instead of width/height changes:
-      ```css
-      /* Bad - causes CLS */
-      .fade-enter-active { height: 0 to 100px; }
-      /* Good - no CLS */
-      .fade-enter-active { transform: scaleY(0) to scaleY(1); }
-      ```
-performance_tips:
-  - "Use Vite for faster development and optimized builds"
-  - "Lazy load routes with dynamic imports"
-  - "Use v-once for static content"
-  - "Use v-memo for expensive list items"
-  - "Consider Nuxt for SSR/SSG"
-migration_paths:
-  nuxt:
-    effort: low
-    benefits:
-      - "Automatic SSR/SSG"
-      - "File-based routing"
-      - "Auto-imports"
-      - "Built-in SEO utilities"
-    guide: "https://nuxt.com/docs/migration/overview"