Search engines and redirects
Updated
These settings are in Site → Main and apply to the whole site. Like everything on your live site, they take effect with your next deploy.
When search engines can see your site
By default, your site is only visible to search engines on your project's domain, the one in the project's Settings. On any other address, including the free Pixexl address, every page carries noindex, nofollow.
That's on purpose. If Google indexed both your free address and your own domain, the two would compete with each other. So once your site runs on your domain (how), it becomes visible there on its own.
The Search engines card shows where your site stands: Visible to search engines or Hidden from search engines, and on which address.
To let search engines index the site on any address, tick Let search engines index the site on any address. Only do this if the free address is the one you want people to find. Pages you hid in their own settings stay hidden either way.
Redirects
A redirect sends visitors, and search engines, from an old address to a new one. Use one when a page is removed or replaced, so old links keep working and the address keeps its rankings.
In the Redirects card, add a rule with:
- From: the old path, like
/old-menu. - To: one of your pages, or another path or full URL.
- Type: Permanent (301) when the move is for good, which is almost always; Temporary (302) for a short-term change, like a seasonal page.
You don't need a rule for pages you renamed in Pixexl: when a published page's slug changes, a redirect from its old address is added for you and listed under From renamed pages. A rule of yours with the same path replaces it. If a page now lives at the address you redirect from, visitors see the page instead.
Moving to Pixexl from another website? Add a redirect for each important old address that changed, so you don't lose the rankings it built.
Google Tag Manager
To measure visits with Google Analytics or another tool, enter your Google Tag Manager container ID (it starts with GTM-) in Site → Main. The container is added to every page on the next deploy, and you manage the tags themselves in Google Tag Manager.