Your first project

Connect a site, verify the installation and enable your first automations.

A "project" in Tuurbo is a website: its connectors, automations, knowledge, audits and history. This page explains how to set one up properly, because most later problems are setup problems.

1. Decide the scope of the project

One project = one domain. Use separate projects for:

separate brands or legal entities;
separate domains (brand.com and brand.de);
staging vs production.

Language subfolders on the same domain stay in the same project.

2. Connect the platform, not just the domain

Adding the domain lets Tuurbo crawl your pages. Connecting the platform lets Tuurbo write back. You need the connector if you want:

product titles, descriptions, attributes and images written to your catalogue;
meta tags published without the script layer;
collection and category content updates.

See eCommerce platforms for the exact steps per platform.

3. Install and verify the script

Use one-click install where available, or paste the snippet as high as possible in <head>.
Publish the theme/template change.
Run Verify in Tuurbo.
If it fails: purge your CDN and page cache, then verify again.

The script is what applies on-page optimizations and measures AI referrals, so nothing else should be configured until verification is green.

4. Fill in Knowledge before generating anything

The Knowledge base is the difference between generic AI text and text that sounds like your brand. Add at least:

a short brand description and value proposition;
tone of voice rules (formal/informal, words to avoid, claims you cannot make);
your product taxonomy or category logic;
key commercial information: shipping, returns, warranty, USPs.

5. Choose the first automations

Do not switch everything on at once. A good starting set:

Missing meta descriptions.
Missing or duplicated title tags.
Missing image alt text.
Open Graph / social cards.

Add GEO/AEO structured data once the basics are clean.

6. Run the baseline audit

Save the first audit as your baseline. Every later report compares against it, which is what makes progress provable to a client or a manager.

7. Plan the first month

Week	Focus
1	Setup, verification, baseline audit, quick wins
2	Product content on the top-selling collection
3	Performance layer and Core Web Vitals
4	Accessibility pass + first report

Checklist before you call setup done

Script verified.
Platform connector active.
Search Console and GA4 connected.
Knowledge base filled.
At least 3 automations active.
Baseline audit saved.