Articles on: Share & analyse

Maglr and SEO

A project published with Maglr is a static website that search engines can crawl and index. Maglr adds the technical SEO basics to every published page automatically: a sitemap, meta tags, structured data and a language declaration. You control whether a domain is indexed at all, and you can adjust each page's meta title, meta description, URL and accessibility structure.


Search engines matter most for inbound content, such as white papers, e-books, infographics and brochures that people find by searching. For content you send out yourself, through email, social media or an intranet, search engines play a smaller role.


Allowing search engines to index your domain


Whether search engines index your Maglr pages is set per domain, with the Index for search engines setting in that domain's settings. A domain you add starts with this setting turned off, so check that it is on for every domain you want to appear in search results.


To turn on indexing for a domain:


  1. In the dashboard, go to Settings → Domain names in the top menu.
  2. Click the pencil icon next to the domain your project is published on.
  3. Turn on Index for search engines.
  4. Click Save changes.


When Index for search engines is on for a domain:


  • Every page on that domain tells search engines it may be indexed and its links followed.
  • The domain's robots.txt allows crawling and points search engines to the sitemap.
  • The domain's sitemap is available at yourdomain.com/sitemap.xml.


When Index for search engines is off for a domain, every page on that domain tells search engines not to index it, the robots.txt blocks crawling, and yourdomain.com/sitemap.xml isn't available. Pages that are already in search results take some time to disappear after you turn indexing off.


The setting applies to all projects on the domain. You can't turn indexing on or off for a single project.


Pages search engines don't index


Even when Index for search engines is on, Maglr keeps these pages out of search results:


  • The automatic www. or root version of a domain you connected (for example example.com when you connected www.example.com). It redirects visitors to the domain you connected, and that domain is the one search engines index.
  • Pages that a visitor views after logging in, such as pages of a secured project.
  • Personalized links (URLs that contain personalization_hash).


What Maglr adds to every published page


Sitemap


Maglr generates a sitemap for a project each time you publish it. The sitemap lists the pages of the project, so search engines can see which pages exist. The domain's sitemap at yourdomain.com/sitemap.xml is an index of the sitemaps of all projects on that domain. It is only available while Index for search engines is on for the domain.


Meta tags


Every published Maglr page gets meta tags for search engines and for social media (Open Graph tags for Facebook and LinkedIn, and card tags for X/Twitter). The tags contain the page's title, description and thumbnail image. Search engines show the title and description in search results, and social media show the title, description and image when someone shares the page. To change these tags, see Adjusting meta tags for a project or page.


Structured data (schema.org)


Maglr adds structured data in schema.org format to every published page automatically. It describes the page to search engines in a standard format and contains up to three parts:


  • Article: the page's headline, description, image, publisher and author (your brand name), publication and modification dates, and your logo.
  • WebSite: the name and URL of the site.
  • BreadcrumbList: where the page sits within the project (for projects with more than one page).


You don't need to set anything for this.


Language declaration


Each published Maglr page tells search engines which language it is written in.


Secure connection (SSL)


All domains that publish Maglr content use an SSL certificate, so pages load over a secure HTTPS connection. This includes Maglr's default domains and your own custom domain connected through DNS. Search engines expect a secure connection.


Hosting and page speed


Page speed affects search ranking. Published Maglr content is stored at AWS in Frankfurt, Germany, and delivered through the Cloudflare CDN, so pages load fast for visitors worldwide. How fast a page loads also depends on how much content you put on it. Click here for more info on hosting.


Responsive pages


Published Maglr pages are responsive, which is what Google's mobile-first indexing expects. For pages you design in freeform mode, you arrange the mobile layout yourself in the editor.


Settings that improve your SEO


Adjusting meta tags for a project or page


You can set a meta title and meta description for a whole project and for each page:


  • Project: Project settings → SEO → Meta title and Meta description.
  • Page: Page settings → SEO → Meta title, Meta description and Canonical link.


A page uses its own meta title and meta description first. If a page has no meta title, Maglr combines the page title with the project's meta title, or with the project title if the project has none. If a page has no meta description, it uses the project's meta description, and if the project has none, the default description set in the navigation environment. The image shown when a page is shared is the page thumbnail, which you can replace in Page settings → Page thumbnail. Click here for more info on meta tags in Maglr.


Changing a page's URL


Each Maglr page has a readable URL in the format domain.com/projectname/pagename, which helps both visitors and search engines. To change a page's URL, open Page settings, and on the General tab click Customize next to URL.


Structuring pages with the accessibility editor


The accessibility editor in the Maglr editor lets you add structure to a page: headings, link names and image descriptions. This structure makes the page accessible for screen readers and easier for search engines to read. Click here for more info on accessibility in Maglr.


Measuring search performance


Connecting Google Search Console


Google Search Console shows how your Maglr pages perform in Google search and reports indexing errors. You connect it per domain with Google's HTML file verification method:


  1. In Google Search Console, add a URL prefix property for your Maglr domain (for example https://magazine.yourdomain.com) and choose the HTML file verification method.
  2. Copy the complete name of the HTML file Google gives you.
  3. In the Maglr dashboard, go to Settings → Domain names in the top menu.
  4. Click the pencil icon next to the domain you added in Google Search Console.
  5. Paste the file name into Google Search Console implementation.
  6. Click Save changes.
  7. Go back to Google Search Console and click Verify.


Google Analytics and Maglr statistics


Standard Maglr statistics are on by default for every domain. You can also connect Google Analytics to a domain: in the domain's settings, turn on Google Analytics or GTM, set Integration type to Google Analytics, and paste your code into GA4 code. Google Analytics then receives page views, clicks and other interactions, and shows how your organic search traffic performs. Click here for more info on integrating Google Analytics with Maglr.


Google Tag Manager


For a more advanced setup, you can connect Google Tag Manager to a domain: in the domain's settings, turn on Google Analytics or GTM, set Integration type to Google Tag Manager, and paste your container ID into GTM code. Maglr sends its events to the Google Tag Manager dataLayer, so you can use them for third-party tools and tracking codes. Click here for more info on integrating Google Tag Manager with Maglr.


Checking which pages Google has indexed


To see which of your Maglr pages Google has indexed, search Google for site: followed by your domain or project URL, for example site:magazine.yourdomain.com. You can also search for a phrase that appears on one of your pages.


Image: viewing the publication via Google Search


Publishing inside your own website


Maglr content is published on a subdomain by default: either a Maglr subdomain or your own custom subdomain (name.domain.com). A subdomain is a new site for Google, so it doesn't benefit from the authority and backlinks your main website has built up. If that matters for your content, you can place it inside your own website instead.


Embedding a page with Automatic format (inject)


When you embed a single page in your website, the default embed option is Automatic format (inject). It places the page's HTML directly in your web page, for example an infographic inside a blog post or a campaign page between your website's header and footer. Search engines then see the content as part of your website. Embedding a whole project uses an iframe instead. Click here for more info on the HTML inject embed option.


Publishing in a subfolder with local sync (Enterprise license required)


You can't point a subfolder of your website (domain.com/folder/) to Maglr's servers: a connected domain is always a subdomain or a whole domain. With an Enterprise license, Maglr can instead publish and sync your content to your own hosting environment, in a subfolder of your choice. Updates are pushed from the Maglr dashboard to your server, the content works independently of Maglr's servers, and it looks the same as when Maglr hosts it. Click here for more info on the local sync option.


Search ranking factors outside Maglr


Maglr handles the technical SEO of your pages, but technical SEO is only part of how search engines rank a page. Your content, the links to your pages from other websites and the authority of your domain also count, and Maglr has no direct influence on these. Maglr can't guarantee a search ranking. A page coded by hand gives a developer more control over every SEO detail; Maglr handles the technical basics automatically, so you don't need a developer.


Frequently asked questions


Why isn't my Maglr project showing up in Google?


Check these causes:


  • Index for search engines is off for the domain the project is published on. A domain you add starts with it off. Turn it on in Settings → Domain names → the pencil icon next to the domain.
  • The project is secured with a login. Pages viewed after logging in are not indexed.
  • Google hasn't crawled the pages yet. New pages can take some time to appear.


To see which pages Google has indexed, search Google for site: followed by your domain, for example site:magazine.yourdomain.com.


Where can I find my project's sitemap?


The sitemap of a Maglr domain is at yourdomain.com/sitemap.xml. It lists the sitemaps of all projects on that domain, which Maglr updates each time you publish. The sitemap is only available while Index for search engines is on for the domain.


Can I stop search engines from indexing my publication?


Yes. Turn off Index for search engines in the settings of the domain the publication is published on (Settings → Domain names → the pencil icon next to the domain) and click Save changes. The setting applies to every project on that domain, not to a single project. Pages that are already in search results take some time to disappear.


Can I publish Maglr content in a subfolder of my own website?


Yes, in two ways. With an Enterprise license, Maglr can sync your published content to a subfolder on your own server (local sync). You can also embed a single page in your website with the Automatic format (inject) embed option, which places the page's HTML directly in your web page (inject embed). You can't point a subfolder of your website to Maglr's servers through DNS.

Updated on: 19/10/2026