GeezerVison is showing github.com — fix: 301 old /api/classes/classes/* phpDocumentor URLs by mychidarko · Pull Request #144 · leafsphp/docs
Conversation
About a quarter of leafphp.dev pageviews land on old phpDocumentor URLs under /api/classes/classes/*.html and get a 404 (bounce ~0.97). Most of that traffic is Google search for Eloquent/Illuminate classes.
This adds 301s to src/public/_redirects:
- The pages with the most traffic go to the closest docs page: Router to routing, Db-Core to database, App to the intro, Http-Request to request, Date to date, Exception-* to error handling, Aloe-Command to writing commands, Symfony Console Command to MVC console, and Illuminate Eloquent Model/Concerns (HasAttributes, HasRelationships, HasEvents and a few more) to database models.
- Every other Leaf class that still has an API page loses the doubled
classes/ segment, so /api/classes/classes/Leaf-Auth.html goes to /api/classes/Leaf-Auth.html.
- Anything else under
/api/classes/classes/ goes to /docs/.
- The Illuminate/Symfony names also get a 301 at
/api/classes/<name>.html, because those vendor pages aren't in the current build.
Existing /api/classes/*.html pages aren't touched. Netlify serves an existing file before it applies a non-forced rule, and none of these rules are forced.
The doubled path probably comes from relative classes/... links combined with <base href="../"> when a page was reached with a trailing slash. If it keeps showing up, we can regenerate the API docs with absolute links.
Generated by a script, so the list can be rebuilt if the API build changes.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
netlify
Bot
commented
Nov 9, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This branch has not been deployed
No deployments
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.