Per-Page Control
When Per-page Control is on (the default), a ScraperBlock box appears in the editor for posts and pages with one option:
| Option | Description |
|---|---|
| Disable protection for this page/post | Bots on the blocklist can load this post or page - it isn't blocked with a 403 |
The setting is saved as the _scraperblock_disable_protection post meta (yes). It also works for the WooCommerce Shop page if you set it on that page.
When to use it: for public content you want every crawler to read, such as a press release or a page meant to be shared on social media.
Per-page control only affects runtime blocking. The noai meta tags and robots.txt rules still apply site-wide, and .htaccess rules (if enabled) aren't page-aware.