How the Validation Bot Works

Overview

The Validation Bot is our post-deployment verification agent. Once a code patch is deployed to your live site, the bot requests the page, bypasses regional caching using cache-busting headers, parses the live HTML DOM, and checks for the exact presence of the injected meta tags.

Prerequisites

• A patch successfully deployed (status: Applied).

Step-by-Step Guide

1. Once a fix is applied, CrawlSage schedules a verification job (typically within 30-90 seconds).
2. The Validation Bot requests the target page URL, appending a cache-busting parameter (e.g. ?cs_nocache=1) to force server-side rendering.
3. The bot searches the header nodes for the custom identifier signature (e.g., <meta name="crawlsage-verification" content="...">).
4. If the signature and code match, the bot updates the database, marking the optimization status as Verified.
5. If missing, the bot schedules two retries before flagging the deployment as Failed.

Expected Result

The optimization item in your dashboard will display a green check badge labeled **Verified**. The overall project health score will automatically update to reflect the correction of this SEO issue.

Common Mistakes

• Manually deploying duplicate tags: If you write the same meta description manually while the bot is verifying, it can detect duplicate tags and flag a syntax conflict.

Troubleshooting

• Verification fails despite tag being live:

  Clear your site cache (W3 Total Cache, Cloudflare, etc.) and click the **Verify Connection** trigger to manually re-run the verification crawler.

Related Guides

• Understanding the Deploy Pipeline
• How to Revert Deployed Patches
• Troubleshooting Deployment Failures