Setup guide · Netlify

Serve ConveyLoop’s SEO pages from a static site on Netlify

Three rewrite rules and one line in robots.txt. No code, and no build step.

← How Git publishing works

Before you start

  • A static site that Netlify deploys from a repository on GitHub.com, GitLab.com or Bitbucket Cloud: HTML files you commit, which Netlify publishes as they are.
  • Built with a framework, such as Next.js, Astro or Hugo? This guide isn’t the one: the framework decides what gets published. For Next.js, see the Next.js guide.
  • Tested on Netlify’s free plan with its default settings, and the connection’s defaults: Standalone HTML, the Target subdirectory /conveyloop/seo, and pages served at /guides. If yours differ, the Git window shows them: use your values where the rules have these.

1. Connect your repository

In ConveyLoop, open Project setup and connect Git. Choose the repository and the branch Netlify publishes from, and keep Standalone HTML: each page is then a complete document with ConveyLoop Metrics built in, which Netlify serves as it is.

Netlify publishes one folder of your repository: the Publish directory in its build settings, or the repository itself when that is empty. ConveyLoop’s folder has to be inside it:

  • Publish directory empty: keep the Target subdirectory /conveyloop/seo.
  • Publish directory set, for example to public: set the Target subdirectory to /public/conveyloop/seo. The rules below stay exactly the same, because Netlify serves the folder at /conveyloop/seo either way.

2. Add the rewrite rules

Put these lines in a file named _redirects at the top of the folder Netlify publishes, next to your home page.

_redirects
# ConveyLoop's pages, served at /guides
/guides               /conveyloop/seo/content/_index.html   200
/guides/sitemap.xml   /conveyloop/seo/sitemap.xml           200
/guides/*             /conveyloop/seo/content/:splat        200
  • The 200 makes each rule a rewrite: the address stays /guides/example-page, and Netlify answers with the file from ConveyLoop’s folder.
  • The last rule serves the pages and their stylesheets. Netlify finds example-page.html for example-page on its own. Any other address under /guides is your site’s 404.
  • Already have a _redirects file? Add these lines above any rule that matches everything, such as /* /index.html 200: Netlify uses the first rule that matches.
  • Serving under another path, such as /learn? Change /guides at the start of each rule.
  • Netlify also serves the folder itself, at /conveyloop/seo/, as it does every file it publishes. Each page’s canonical link names its /guides address, so that is the one search engines index.

3. Point search engines at the sitemap

The second rule serves the sitemap ConveyLoop keeps in its folder. Add its address to your robots.txt, using your site’s address, the same one your ConveyLoop project has. No robots.txt yet? Create one in the same folder as _redirects:

robots.txt
User-agent: *
Allow: /

Sitemap: https://www.example.com/guides/sitemap.xml

Already have one? Add just the Sitemap: line. A site can list several, so keep any you have. Search engines and ConveyLoop’s own crawl both read it.

4. Let ConveyLoop read the pages

  • In Netlify, open Project configuration → General → Visitor access. If the project is Private or has a password, every visitor without a login gets a 401, ConveyLoop and search engines included. Set it to Public. We found a new project set to Private.
  • If you put a firewall or bot protection in front of the site, allow requests whose User-Agent starts with ConveyLoopBot or ConveyLoop-Crawler for your public pages, /guides among them, plus /robots.txt and /sitemap.xml (or the sitemap your robots.txt names). The crawl starts at your homepage, so allowing only /guides isn’t enough. Keep the protection for everything else, such as login and account pages: a User-Agent is easy to fake.

5. Publish and check

Commit the two files, then publish a page. Each publish is a commit, and Netlify deploys every commit to your production branch: in our test, a new page was live ten seconds after it was committed. A few minutes after a publish, ConveyLoop fetches the page at its address, and the Git window shows Live on your site.

If the page isn’t there, the Git window says what ConveyLoop found instead and gives you a prompt for your AI coding agent that fixes it. Also check Netlify’s Deploys page: while auto publishing is locked, Netlify builds each commit but doesn’t publish it.

Let your Netlify site publish its own SEO pages

Add the rules once. ConveyLoop writes the pages, commits them and keeps improving them.