Non-WordPress sites
Trovavio on your non-WordPress site too
The WordPress plugin publishes the corrections you approve on your site. If your site is built with Wix, Squarespace, Shopify, Webflow, Joomla, Drupal, PrestaShop, or written in code (HTML, React, Next.js, Laravel, Python, Node), the result is the same: you connect the site once, and from then on you apply the corrections from the Trovavio dashboard, without copying and pasting each time.
You connect from the dashboard, in the “Connect the site” section: choose how your site is built and we give you the ready-made code, with the instructions.
Create an accountWhere corrections are applied: from Trovavio
After connecting, corrections are written, approved and applied from the Trovavio dashboard. You don't have to go back to your site.
- You approve in Trovavio. In “What to fix” you press “Apply to your site”: you see the proposal and approve it.
- The code on your site reads it. The code you pasted once asks Trovavio for the approved corrections for each page.
- The page comes out corrected. Google, and with the server-side channels the AI assistants too, read the new title, description and structured data.
Trovavio doesn't get into your site. It doesn't have your passwords and can't see your files: it's the code you pasted that comes to fetch the corrections you approved.
They aren't instant: they reach the site within 5 minutes with the script and within an hour with PHP, Worker and Node. Every correction can be undone with one click.
What it applies to your site
It changes the part of the page that visitors don't see, the part that Google and AI assistants read. The text and images stay the ones you wrote.
- Title and description. For every page, written from the page's real content.
- Social preview. The title and description that appear when the link is shared (Open Graph).
- Structured data. For example the business, the local listing or the frequently asked questions: they tell search engines who you are and what you do.
- The llms.txt file and the rules for AI assistant bots. Where the channel allows it: the table below says where.
- Keywords. Only if you want them. Google has ignored them for years: we support them because some tools and some people ask for them, not because they move you up the rankings.
You see and approve every correction before it is applied.
How to connect, in three steps
- What kind of site do you have? Choose the platform: we tell you the simplest way and what changes for Google and for AI assistants.
- Paste this. You copy the code, already filled in, and paste it where the instructions for your platform say.
- Verify the connection. A button looks at your site and says whether the code is there. From then on you see the status, the last contact and the active corrections.
Four ways, and what changes
The simplest way is the script, but it isn't the most complete. We say so up front, so you choose knowing it.
| Method | Where it runs | AI assistants without JavaScript | llms.txt and AI bots | |
|---|---|---|---|---|
| Script | In the visitor's browser | Reads them, with a slight delay | Don't see them | No |
| PHP file | On the site's server | Finds them already in the page | See them | Yes, if the site doesn't already have its own file |
| Cloudflare Worker | In front of the site, on Cloudflare | Finds them already in the page | See them | Yes, if the site doesn't already have its own file |
| Node middleware | On the site's Node server | Finds them already in the page | See them | Yes, if the site doesn't already have its own file |
Which to choose. For Wix, Squarespace, Shopify and Webflow you use the script, because the code is pasted from the settings and server files can't be touched. For Joomla, Drupal, PrestaShop and custom PHP sites the PHP file is the better choice. If the domain goes through Cloudflare there is the Worker, which works for any site. For an Express site there is the Node middleware. If you don't know what kind of site you have, start with the script.
The Cloudflare Worker is the newest channel: after turning it on, the “Verify the connection” button tells you whether it responds, and it's worth checking a page of the site.
Corrections reach the site within 5 minutes with the script and within an hour with PHP, Worker and Node.
Is your site written in code?
It works even if the site isn't built with a site builder: hand-written HTML, React, Next.js, Laravel, Python or anything else. The script line goes in the head of the pages, and it works for any site whose code you can edit.
To reach the AI assistants too, the corrections must already come out of the server: a PHP file, a Cloudflare Worker if the domain goes through it, or the middleware for Node and Express. For frameworks like Next.js there is no dedicated package yet, and we'd rather say so.
Does a developer manage the site? From the dashboard you copy a ready-made message to send them: what to add, where, and how to check it.
If you'd rather not connect anything
Corrections stay useful even without a connection: you copy each proposal and put it in yourself, where needed. Nothing is automatic.
Security
- No password and no access to your files. We don't ask for your site credentials or FTP access.
- A single code, which you can revoke. The code doesn't contain your plan's key: you can regenerate or disconnect it at any time, and the old one stops working immediately.
- It doesn't modify your files. The code is added to the site; it doesn't replace anything you have.
- If anything goes wrong, the site stays as it is. If Trovavio doesn't respond or the code meets a page it can't read, the page goes out as you wrote it.
- No cookies. The code stores nothing in the browser of whoever visits the site.
Privacy: what Trovavio sees
Connecting a site doesn't give Trovavio access to its visitors. Here is what really happens, channel by channel.
- What the code reads. It downloads the list of the site's corrections and looks up the page's one in the browser: the page address is not sent to Trovavio. It doesn't read cookies, forms, texts or data of whoever is browsing.
- What we keep. The last contact and the channel used. No addresses of visited pages, no IP address and no data of whoever visits the site in our database.
- With the script. The browser of whoever visits the site contacts our servers, as with an embedded font or map. The server that answers sees the IP address in order to respond and to limit abuse (in memory, for one minute), but does not record or keep it. If you use the script, it may be worth naming it among the external services in your site's privacy notice.
- With PHP, Worker and Node. Whoever visits the site never contacts Trovavio: your server asks for the corrections, at most once an hour, without any data of whoever is browsing. It is the most private channel.
The details, including data retention and your rights, are in the privacy policy.
From which plan, and how many sites
Connecting a site without WordPress is included from the Solo plan; the free plan doesn't include it. Connected sites follow the plan limit: 1 with Solo, 3 with Pro, 15 with Agency. Every proposal written by the AI uses 1 credit; the rules for AI assistant bots are written by our code and use none.
Plans and prices · All features · The WordPress plugin
Questions
Where do I apply the corrections, after connecting the site?
Does Trovavio get into my site?
My site is written in code: does it work?
Do I need to install a plugin?
What changes on my site?
With the script, does Google see the corrections?
Do keywords move you up on Google?
Can I go back?
How much does it cost, and how many sites can I connect?
Plugin or connector: not sure which one your site needs? Read the difference in the glossary
Connect your site in a few minutes
You create the account, choose the platform and paste the code. Then you approve the corrections yourself, one by one.