<2-3 sentences summarising what the project addresses and solves, the target audience, and the benefit.> This package scans Laravel application routes to identify SEO improvements. It targets Laravel developers seeking to enhance their website's search engine ranking by providing automated checks for performance, content quality, meta tags, and configurations. The tool offers detailed insights and actionable suggestions to boost SEO scores.

How It Works

The scanner analyzes your Laravel application by crawling defined routes or specific URLs. It performs a comprehensive suite of checks (over 24, categorized into Configuration, Content, Meta, Performance, Security, and AI) based on SEO best practices. Users can customize which routes to scan, exclude specific checks, and even add their own custom validation logic, making it highly adaptable to project-specific needs.

Quick Start & Requirements

• Installation: composer require backstage/laravel-seo-scanner
• Prerequisites: PHP 8.2+, Laravel 12.0+. For JavaScript-rendered pages (SPAs), install Puppeteer: npm install puppeteer.
• Setup: Run php artisan seo:install to publish configuration and migrations.
• Docs: Configuration details available in config/seo.php.

Highlighted Details

• Integrates with Google PageSpeed Insights API for Core Web Vitals and performance scores (opt-in).
• Supports scanning JavaScript-rendered SPAs using Puppeteer.
• Handles large sites efficiently by splitting scans into batched queue jobs, preventing timeouts and managing memory.
• Allows saving scan results to the database and associating scores directly with Eloquent models via a trait and interface.

Maintenance & Community

The project lists its primary contributors and provides links to contribution, changelog, and security policy documentation. No specific community channels (like Discord/Slack) are mentioned in the README.

Licensing & Compatibility

Licensed under the MIT License, permitting commercial use and integration into closed-source applications.

Limitations & Caveats

Scanning SPA routes requires an additional npm install puppeteer step. PageSpeed Insights checks are opt-in and rely on an external API key, potentially introducing rate limits and slower execution. The README does not detail specific known bugs or alpha/beta status.