/license.xml, fetches and caches your license from Supertab Connect, and validates Authorization: License tokens on automated requests.
- Requirements: WordPress 6.4 or higher (self-hosted or WordPress VIP).
- Plugin: Supertab Connect
Before You Start
You need:- A Supertab Connect merchant account – contact sales to sign up
- A Website registered in the dashboard — select WordPress as the integration type
- Your Website URN — found in Website settings, looks like
urn:stc:merchant:system:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Install the Plugin
In your WordPress admin, go to Plugins → Add Plugin, search for Supertab Connect, install, and activate. The plugin will redirect you to its settings page on first activation.Configure RSL
In Settings → Supertab Connect, paste your Website URN into the Website URN field and save. Once saved, visithttps://yourdomain.com/license.xml to confirm your RSL license is being served.
If the license doesn’t reflect recent changes, your hosting stack may have a caching layer in front of WordPress. Purge the cache for
/license.xml from your host’s control panel.Configure CAP
Generate a Merchant API key
In the Supertab Connect dashboard:
- Open your Website Details
- Go to the API Keys section
- Click Generate new key
- Copy the generated key
Enable CAP in the plugin
In WordPress, go to Settings → Supertab Connect:
- Find the License Verification section
- Paste the generated Merchant API key into the Merchant API key field
- Click the Enable CAP checkbox
- Click Save Changes
Configure Active Paths
By default, CAP protects your entire site using a single
* wildcard path. You can narrow protection to specific sections of your site.- In the Active Paths section, review the default path
- Optionally remove
*and add specific path patterns - Click Add Path to add additional patterns
- Click Save Changes
| Pattern | Matches |
|---|---|
* | Entire site (default) |
blog/* | All URLs under /blog/ |
premium/* | All URLs under /premium/ |
pricing | Only the /pricing page |
Paths support
* for wildcards. Both /sample-page and /sample-page/ (trailing slash) are treated as the same path.Update robots.txt
Add aLicense: directive to your robots.txt so crawlers can discover your license:
User-agent: directives.
Publishing New Versions
When you publish a new version of your RSL license, click Deploy in the RSL Editor and choose Manual Deployment. Follow the on-screen steps to refresh the license on your WordPress site.Troubleshooting
| Problem | What to check |
|---|---|
license.xml returns 404 | Confirm the Website URN is saved correctly in plugin settings |
| CAP is not enforcing | Confirm the CAP checkbox is enabled, the API key matches the current key in the dashboard, and the plugin settings were saved |
| License shows stale content | Purge your hosting cache for /license.xml |
| Human visitors are being blocked | Check that your WordPress permalink settings are not interfering with the plugin’s request interception |
| CAP verification fails in dashboard | Confirm the Merchant API key in WordPress matches the current key in Supertab Connect |
Next Steps
Acquire Licenses
Test the protected flow by obtaining a license token and making a licensed request.
Crawler Authentication Protocol
How CAP works, what it enforces, and what it leaves to you.