laravel-seo-scanner

Scan your Laravel application routes for SEO improvements suggestions.

Runs with mockssource: GitHubPHPMITcommit 6a3b55056708

PHP, MIT licensed. The project labels itself: crawler, laravel, laravel framework, laravel seo, laravel seo scanner, scanner, seo and seo optimization.

laravel-seo-scanner runs, with stand-ins for the services it depends on. An Argusic agent installed it in 9 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

composer install works, the full Pest suite passes (171 passed, 3 skipped), PHPStan passes, and seo:scan-url returns real results (score 65, 28 passed, 15 failed) plus seo:scan persists the score to MariaDB, all against local mocks in this container.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.73 (measured)
recorded runs
1
last tested
stars
275
forks
31
open issues
2
watchers
4
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing laravel-seo-scanner, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • No php/composer in container (no root): used prebuilt static PHP 8.4.23 + Composer 2.10.3 to install 138 packages3 minutes
  • Real seo:scan-url returned empty checks (score 0, 0 checks): config check_paths pointed to base_path('vendor/backstage/laravel-seo-scanner/src/Checks') which does not exist in this dev-copy install3 minutes
  • composer test failed with /usr/bin/env: php: No such file or directory1 minute
  • composer analyse failed: PHPStan worker hit 128M memory limit1 minute
  • seo:scan with database.save=true failed: Table 'seo_test.seo_scans' doesn't exist1 minute
Install time
9 minutes
Cold machine to finish
28 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
composer test exited 0: 171 passed, 3 skipped (227 assertions); composer analyse -- --memory-limit=1G exited 0: [OK] No errors; php tools/rg-check.php (boots app + package provider, runs seo:scan-url --format=json) exited 0 and printed JSON: url http://127.0.0.1:8123/ score 65 passed 28 failed 15; seo:scan with database.save=true exited 0 and wrote 1 seo_scans row (pages=1) and 1 seo_scores row (score 65) in MariaDB
Model tokens used
3,708,998
Exact commit tested
6a3b55056708
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

tokens used
3,708,998
All verification is complete and reproducible. Here's the report.
**What I did**
- This is a Laravel package (`backstage/laravel-seo-scanner`). No PHP or Composer existed in the co…
- Ran `composer test` → exit 0, **171 passed, 3 skipped** (the 3 skips are explicit `markTestSkippe…
- To exercise the real CLI, I stood up two local mocks, both running and observed: MariaDB 11.4.5 o…
- Ran the actual `seo:scan-url` command via a booted Laravel app with the package provider → exit 0…
**Error found and fixed**
- Bug: in `config/seo.php`, `check_paths` pointed at `base_path('vendor/backstage/laravel-seo-scann…
- Fix: `config/seo.php:72` now uses `dirname(__DIR__).'/src/Checks'`, which is the checks directory…
**Result line** (per the requested format, plain text):

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 9 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 26 crawler projects Argusic has installed and timed, laravel-seo-scanner was the 18th fastest to reach a running state, and 22 of 26 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.73

Topics (from GitHub)

crawlerlaravellaravel-frameworklaravel-seolaravel-seo-scannerscannerseoseo-optimizationseo-toolsseotools

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/laravel-seo-scanner.svg)](https://argusic.com/subject/laravel-seo-scanner)

Questions

Does laravel-seo-scanner run?
laravel-seo-scanner runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test laravel-seo-scanner?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6a3b55056708. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test laravel-seo-scanner?
The run that produced this verdict cost $0.73: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does laravel-seo-scanner take to install?
9 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does laravel-seo-scanner need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing laravel-seo-scanner?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does laravel-seo-scanner compare with the alternatives?
Of the 26 crawler projects Argusic has installed and timed, laravel-seo-scanner was the 18th fastest to reach a running state, and 22 of 26 reached one at all.
Where is the evidence for laravel-seo-scanner?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion