Features
Connect Cloudflare (NeoRank Edge)
Coming soon — For a site on any CMS served through Cloudflare: a Cloudflare Worker applies the fixes you approve in your pages' real HTML, visible to Google and to AI crawlers that run no JavaScript.
What NeoRank Edge is
NeoRank Edge is a Cloudflare Worker in front of your site. When a page goes through Cloudflare it replaces, in the served HTML, only the elements you approved in NeoRank. Your origin server and your CMS are never changed: the fix exists in the page Cloudflare serves.
- The same page for visitors and crawlers; no script added for visitors, no cookie.
- The list of fixes the worker serves is signed by NeoRank; an invalid JSON-LD block is removed.
- At the slightest problem, the worker serves your original page untouched.
Create the Cloudflare API token
- In Cloudflare › My Profile › API Tokens › Create Token › Custom token.
- Add exactly these three permissions, then limit Zone Resources to this site's zone:
Account › Workers Scripts › Edit
Zone › Workers Routes › Edit
Zone › Zone › ReadConnect in three steps
- Create the token above.
- In NeoRank, Settings › Connectors, “Cloudflare — NeoRank Edge” card: paste the token, then “Install NeoRank Edge”. NeoRank checks it, installs the worker and routes your domain through it.
- NeoRank checks your pages answer through the worker. The token is stored encrypted and can be revoked at any time.
Install it yourself, without sharing a token
- “Install it yourself”: download the three files (the worker, wrangler.toml and the steps).
- Run
npx wrangler deployin their folder, signed in to your Cloudflare account. - Come back to NeoRank and check the connection.
What NeoRank can change
| HTML element | Detail |
|---|---|
The <title> tag | — |
| The meta description | — |
| Image alt text | Matched by the image's address |
| JSON-LD structured data | NeoRank's own blocks; an invalid block is removed |
| 301 redirects | Only for pages that return 404 |
Canonical, hreflang, robots, links in content and /llms.txt stay in your hands (guided).
Workers free plan
Check, pause, revoke
- Check the connection: NeoRank checks the site answers through the worker.
- Pause: the worker serves your original pages, without the fixes, until you resume.
- Download the files again for a manual install or a worker update.
- Revoke removes NeoRank's route and worker from Cloudflare (with the token) and deletes the token.
Common problems
| Message | What to do |
|---|---|
| This does not look like a Cloudflare API token | Copy the token itself, not its id. |
| This token is disabled or expired | Re-enable it or create a new one in Cloudflare. |
| Cloudflare refused this token | Create it again with the three exact permissions. |
| The token lacks … Workers Scripts / Workers Routes / Zone Read | Add the permission named and limit it to the site's zone. |
| No Cloudflare zone of this token serves the site's domain | Limit the token to the zone that serves this domain. |
| Another Cloudflare route already covers this site | Another Worker or a “no Worker” route covers the domain: remove it in Workers Routes, or install NeoRank Edge yourself. |
| The site does not answer through NeoRank Edge yet | Check the domain goes through Cloudflare's proxy (orange cloud); it can take a minute, then “Check again”. |
| Old worker version / previous install | Download the install files again and redeploy them with wrangler. |
| Worker installed for another connection | Remove it from Cloudflare, then reinstall from this card. |