Know what pSEO Guard cannot prove yet
A useful quality gate should make its blind spots visible. These are current product boundaries, not conditions that should be read as a pass.
Last updated
Browser audit limits
The current free CSV audit accepts up to 5,000 rows per run. Some content comparisons are bounded for very large page groups, and rows that were not fully compared are reported for review rather than silently passed.
Content checks need content
Body-level checks require content_text. Metadata alone cannot establish that two full pages are meaningfully different.
Cross-template near-duplicate discovery is not exhaustive at every score
Pages that use the same page pattern receive the most complete comparison. Across different patterns, pSEO Guard prioritizes the closest candidates; if a pair was not compared, the result says so instead of treating it as a pass.
Existing Site Guard only knows what it can retrieve
The scan is intentionally bounded and respects robots.txt. It cannot claim there is no collision on pages it did not retrieve, and target intent is not measurable when the live source does not provide that information.
WordPress publishing is available; Search Console monitoring is not
WordPress publishing is Available for the standard Pages contract described in the Connector Docs. Search Console monitoring remains Roadmap, so publishing verification must not be read as Google indexing evidence.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.