-
-
Notifications
You must be signed in to change notification settings - Fork 23
Add comprehensive SEO static checker #424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
99da1e2
Add comprehensive SEO static checker that runs before deployment
riderx d097734
Expand SEO checker: implement 200+ rules from 1152-rule CSV
riderx 89edd91
Fix SonarCloud issues: move rules to JSON, add regex error handling
riderx 286aef1
Add robots.txt and sitemap.xml validation checks
riderx 445c585
perf: optimize SEO checker with parallel processing
riderx ec52005
Migrate to @capgo/seo-checker CLI
riderx 321e08f
chore: update bun.lock
riderx b68fe65
Use GitHub output format for SEO checker
riderx 11242b2
fix: resolve merge conflict in .gitignore
riderx File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,86 @@ | ||
| { | ||
| "distPath": "./dist", | ||
| "baseUrl": "https://capgo.app", | ||
| "languages": [ | ||
| "en", | ||
| "fr", | ||
| "de", | ||
| "es", | ||
| "it", | ||
| "pt", | ||
| "ja", | ||
| "ko", | ||
| "zh", | ||
| "ru", | ||
| "nl", | ||
| "pl", | ||
| "uk", | ||
| "id", | ||
| "ar" | ||
| ], | ||
| "defaultLanguage": "en", | ||
| "rules": { | ||
| "disabled": [ | ||
| "SEO00003", | ||
| "SEO00186", | ||
| "SEO00189", | ||
| "SEO00160", | ||
| "SEO00222", | ||
| "SEO00116", | ||
| "SEO00117", | ||
| "SEO00118", | ||
| "SEO00119", | ||
| "SEO00120", | ||
| "SEO00121", | ||
| "SEO00122", | ||
| "SEO00123", | ||
| "SEO00124", | ||
| "SEO00135", | ||
| "SEO00136", | ||
| "SEO00137", | ||
| "SEO00152", | ||
| "SEO00111", | ||
| "SEO00088", | ||
| "SEO00090", | ||
| "SEO00092", | ||
| "SEO00094", | ||
| "SEO00168", | ||
| "SEO00169", | ||
| "SEO00170", | ||
| "SEO00171", | ||
| "SEO00172", | ||
| "SEO00371", | ||
| "SEO00372", | ||
| "SEO00177", | ||
| "SEO00178", | ||
| "SEO00179", | ||
| "SEO00180", | ||
| "SEO00229", | ||
| "SEO00230", | ||
| "SEO00231", | ||
| "SEO00020", | ||
| "SEO00027", | ||
| "SEO00034", | ||
| "SEO00147", | ||
| "SEO00155", | ||
| "SEO00134", | ||
| "SEO00144", | ||
| "SEO00380", | ||
| "SEO00143", | ||
| "SEO00164", | ||
| "SEO00166", | ||
| "SEO00023", | ||
| "SEO00030", | ||
| "SEO00110", | ||
| "SEO00125", | ||
| "SEO00013", | ||
| "SEO00007" | ||
| ], | ||
| "severityOverrides": {}, | ||
| "thresholdOverrides": {} | ||
| }, | ||
| "exclusions": [], | ||
| "failOn": ["error", "warning"], | ||
| "maxIssues": 0, | ||
| "outputFormat": "console" | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| { | ||
| "$schema": "./seo-checker.exclusions.schema.json", | ||
| "description": "SEO Checker Exclusions - Add specific issues to exclude from the SEO check", | ||
| "exclusions": [] | ||
| } |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Cap-go/website
Length of output: 782
@capgo/seo-checker@0.0.1 is the brand-new, first-ever release of this package—consider the risk of using it in a deployment-blocking context.
This package was published only hours ago and has no release history. Using a completely untested, newly-published package in your
build:afterhook creates significant risk: any latent bugs discovered later could block all deployments. Consider either thoroughly testing this version in non-blocking scenarios first, deferring its use until the package has multiple releases and proven stability, or restructuring your build process so SEO checker failures don't block deployments.