Here you'll find documentation on how Seoella works: installation, how recommendations are reviewed and approved, how technical SEO elements such as canonical and schema are handled, and how to troubleshoot common issues.
Seoella is an SEO platform that analyzes your website, generates recommendations, and can implement the changes you approve directly on the website. This article describes the basic flow and what sets Seoella apart from a traditional audit tool.
The difference from traditional SEO tools
Many SEO tools identify problems and provide recommendations, but the actual change then has to be made manually in the CMS or submitted as a development task. Seoella can also publish the change. The recommendation can be implemented from the platform after approval, without every change first having to become a development task.
How the process works
Install Seoella on the websiteA code snippet is placed in the website's <head>. See Installing Seoella.
Ella analyzes the websiteSeoella's AI, Ella, goes through the pages and presents recommendations.
You review, edit, and approveYou choose which recommendations should be published. Recommendations that aren't approved don't affect the website. Approved changes can then be implemented directly on the website.
What can Seoella do?
The platform consists of several parts that you can use together or separately:
OnPage Automation – analyzes and optimizes things like meta titles, meta descriptions, alt texts, canonical tags, and schema markup. See the review-and-approve flow.
Schema markup – generates JSON-LD tailored to the page's content. See Schema markup.
You don't need to use all of the parts. It's fine to use Seoella solely for, for example, metadata.
Important
The basic principle is that you remain in control of which recommendations are published. The exception to be aware of is schema: once Seoella's schema is approved for a URL, it replaces any existing JSON-LD on that page.
Installing Seoella
The standard installation consists of adding Seoella's code snippet to the website's <head>. Here we go through what you need, how the installation works, and how to check that it's working.
Before you begin
You need to be able to add code to the website's <head>. How this is done depends on your CMS.
Seoella is built to work regardless of CMS as long as the code snippet can be installed. WordPress, Shopify, and Wix are mentioned as examples, and custom-built websites also generally work.
If you use WordPress, there's also a plugin that can apply the changes server-side. See WordPress.
Do we need a developer?
In many cases, no. The installation consists of adding a code snippet, after which the SEO changes are managed from Seoella's interface without requiring ongoing developer involvement.
A developer may, however, be needed for the initial installation if you don't have the means to add code to the website's <head> yourselves.
Step 1: Get the code snippet
The code snippet is displayed in Seoella's interface when you add your website.
HTML – to be placed in <head>
<!-- Seoella: replace with the code snippet shown in your Seoella account -->
<script async src="{{SEOELLA_SNIPPET_URL}}"></script>
Note
The example above is a placeholder. Always use the exact code snippet you receive in Seoella's interface for your website.
Step 2: Add the snippet to <head>
Place the code snippet in the <head> of the website's pages. Most CMS platforms have a setting for "header code" or "custom code" where this can be done without editing theme files.
Step 3: Approve a first recommendation
Once the snippet is installed, Ella can analyze the website and present recommendations. Approve a recommendation, for example a meta description, to verify that the flow works. See Start carefully.
How do I know it's working?
With the standard installation, changes are applied client-side using JavaScript after the HTML page has loaded. This means an approved change won't appear in the page's raw source code (view source), but rather in the rendered page. Therefore, check the current page in your browser's developer tools (Inspect element) instead of the source code.
Note also that the script runs the DOM changes several times after page load (immediately, and again after roughly 1, 3, 6, and 10 seconds) to catch elements that load dynamically. Read more under JavaScript or server-side?.
Common issues
The change isn't showing – check that the recommendation is approved and that you're looking at the rendered page, not the source code. See My changes aren't showing up.
Google still shows the old value – the change on the website takes effect immediately, but Google needs to crawl and process the page before the search result is affected. See When can we expect results?.
Start carefully: a recommended initial setup
You don't need to activate everything at once. A common approach is to start with a limited number of recommendations or categories and expand once the implementation has been verified.
What an initial setup might look like
Choose a narrow categoryStart, for example, with meta titles or meta descriptions. Leave canonical and schema recommendations unapproved for now.
Approve a small number of pagesReview and edit the recommendations before approving them.
Verify on the websiteCheck that the approved change is applied on the page (see How do I know it's working?).
Expand graduallyAdd more categories, more pages, or bulk rules once you're comfortable with the results.
Tip
Only the recommendations you approve affect the website. For example, you can let Seoella handle meta titles, meta descriptions, and alt texts while continuing to manage canonical tags yourself. See Using Seoella for some SEO elements but not others.
Pay extra attention to schema
Schema is the category where it's most important to understand what gets overwritten. Once Seoella's schema is approved for a URL, it becomes the active schema implementation on the page, and existing JSON-LD tags may be replaced or removed. Read Seoella and existing schema before approving schema recommendations.
Think about who "owns" each element
Your developers can still make SEO changes in the CMS. The important thing is to avoid having both the CMS and Seoella trying to control the same element at the same time once Seoella's version has been approved.
How the review-and-approve flow works
Seoella does not publish any OnPage changes automatically. Every recommendation is reviewed, can be edited, and is approved by you before it affects the website.
Does Seoella make changes without my approval?
No. For the standard OnPage recommendations, the basic principle is that you have control over which recommendations are published. If a recommendation is not approved, Seoella does not affect that particular element.
This means, for example, that you can approve Seoella's meta descriptions while leaving your existing canonical tags completely untouched.
Can I edit a recommendation before I approve it?
Yes. Recommendations can be reviewed and adjusted before they are published. Seoella describes this as a review-and-approve flow where the user retains control over the changes.
What happens when I approve?
The approved version is used on the current URL. Seoella applies the changes linked to approved recommendations and leaves unapproved categories untouched. For example, if a meta description is approved but the canonical is not, the meta description changes while the canonical tag is left untouched.
Recommendation status
What Seoella does with the element
Not approved
Nothing. The website's existing value is used.
Approved
Seoella's approved version is used on the URL.
Approved, then revoked (unapproved)
Seoella stops applying the change on the URL.
Can I remove an approved change?
Yes. A previously approved recommendation can be deactivated by revoking it (unapprove). Seoella will then no longer apply that change on the current URL. See Remove or revoke an approved change.
Important about schema
Schema works differently from other categories: when Seoella's schema is approved, existing JSON-LD on the URL is replaced. Read Seoella and existing schema.
Using Seoella for some SEO elements but not others
You can let Seoella handle certain categories, such as meta titles and meta descriptions, while retaining full control over others, such as canonical tags or schema. The key is what you approve.
How you control which elements Seoella affects
There is no separate "on/off" setting per category that is needed. Only the recommendations you choose to approve affect the website. If you want Seoella to leave a certain category alone, you simply leave the recommendations in that category unapproved.
For example, you can:
use Seoella for meta titles
use Seoella for meta descriptions
use Seoella for alt texts
while continuing to manage canonical tags yourselves.
Example: we want to manage canonical ourselves
Leave the canonical recommendations unapproved. If no Seoella recommendation is approved for canonical, Seoella will not change your existing canonical tags. Your own canonical tags can therefore remain static in the HTML while Seoella is used for, for example, meta titles and meta descriptions. Read more in How canonical tags work in Seoella.
Does Seoella rewrite the entire <head> if only one category is approved?
Seoella applies the changes linked to approved recommendations. If a meta description is approved but the canonical is not, the meta description changes while the canonical tag is left untouched.
Can we use Seoella for metadata only?
Yes. You do not need to use all parts of the platform.
Can it be mixed per page?
Yes. Approvals apply per URL. You can, for example, approve Seoella's schema on certain URLs and leave the others unapproved, so that the website's own schema is used there. See Schema markup.
Remove or revoke an approved change
Have you approved a recommendation that you want to undo? Revoke it (unapprove), and Seoella will stop applying the change on the current URL.
How revoking works
A previously approved recommendation can be deactivated by revoking it. Seoella will then no longer apply that change on the URL, and the website's own value is used instead.
When is this particularly relevant?
You want to use your own schema again. Revoke Seoella's schema on the relevant URLs. After that, the website's own schema implementation (for example via Yoast, Rank Math, or custom code) can be used. See Seoella and existing schema.
You want to let the CMS control an element. Avoid having both the CMS and Seoella try to control the same element at the same time. Revoke Seoella's version before the developers take over the element.
Note
Removing the change from the website does not mean Google's search results update immediately. Google must crawl and process the page again. See When can we expect results?.
Bulk optimization and large websites
Seoella is built to handle large volumes of pages and changes, with support for rules that are applied across larger parts of the website.
Can Seoella handle large websites?
Yes. Seoella is built for bulk optimization and is used to handle large volumes of pages and changes. The platform describes the ability to publish anywhere from hundreds of thousands to millions of OnPage changes.
Can the same SEO change be made across many pages at once?
Yes. Seoella supports rules and bulk optimizations that can be applied across larger parts of the website.
What happens when new pages are created?
Seoella describes the platform as built to continue analyzing the website as content changes or new pages are added.
Tips for larger websites
Websites with strict performance requirements should continue monitoring LCP, INP, and CLS after installation. See Performance and Core Web Vitals.
Can Seoella harm our existing SEO?
The basic principle is that changes are reviewed and approved before they are activated. The most important thing to avoid unwanted effects is to understand which categories are actually overwritten when they are approved.
Control before changes go live
Seoella markets this as "full control before changes go live". Unapproved recommendations do not affect the website, and approved recommendations can be revoked.
What gets overwritten when it is approved?
Category
What happens to the website's existing value when Seoella's version is approved
Meta title
Seoella's approved version is used on the URL.
Meta description
Seoella's approved version is used on the URL.
Canonical
Seoella's approved version is used on the URL.
Schema (JSON-LD)
Seoella's JSON-LD becomes the active schema implementation. Existing JSON-LD tags are replaced or removed on the URL.
Yes. A common approach is to start with a limited number of recommendations or categories and then expand once the implementation has been verified. See Start carefully.
Can our developers still make SEO changes in the CMS?
Yes. The important thing is to avoid having both the CMS and Seoella try to control the same element at the same time if Seoella's version is approved.
Meta titles and meta descriptions
OnPage Automation analyzes and optimizes, among other things, metadata on the website's pages. This describes how Seoella's suggestions relate to your existing meta titles and meta descriptions.
Can Seoella create meta titles and meta descriptions?
Yes. OnPage Automation is built to analyze and optimize, among other things, metadata on the website's pages.
Can I edit Seoella's suggestion?
Yes. The recommendation can be edited before it is approved.
What happens to our existing meta description?
If no Seoella recommendation is approved, the website's existing meta description is used.
If a Seoella recommendation is approved, the approved version is used.
The same principle applies to meta titles.
Technical
With the standard installation, the metadata changes are applied with JavaScript after page load. Since the elements are located in <head>, they do not affect the page's visual layout, and Google and Bing can render JavaScript. For maximum accessibility for other crawlers, a server-side implementation is available via the WordPress plugin. See JavaScript or server-side?.
How canonical tags work in Seoella
Seoella does not touch your canonical tags if no canonical recommendation is approved. You can therefore keep your own canonical tags while also using Seoella for other categories.
What happens if the website already has a canonical tag?
If no Seoella canonical is approved, the website's existing canonical is left untouched.
What happens if I approve a canonical in Seoella?
The approved Seoella version is used on the current URL.
Can we use our own canonical tags together with Seoella?
Yes. Leave the canonical recommendations in Seoella unapproved and use Seoella for the other categories you want to optimize. Your canonical tags can remain static in the HTML while Seoella handles, for example, meta titles and meta descriptions.
Does the canonical logic still run if canonical is not approved?
The relevant effect is that Seoella should not change the canonical tag when no canonical recommendation is approved. For example, if a meta description is approved but the canonical is not, the meta description changes while the canonical tag is left untouched.
Recommendation
Decide who "owns" canonical: the CMS or Seoella. Avoid having both try to control the same element at the same time when Seoella's version is approved.
Schema markup (JSON-LD)
Ella analyzes the page's content and can generate JSON-LD based structured data tailored to the page. The recommendation can be reviewed and adjusted before it is published.
Can Seoella generate schema markup?
Yes. Ella analyzes the page's content and generates JSON-LD tailored to the page. You can review and adjust the recommendation before approving it.
Can I use Seoella's schema on some pages and my own schema on others?
Yes. Approve Seoella's schema on the URLs where you want to use it and leave the other URLs unapproved. On unapproved URLs, the website's own schema is used.
What happens if there is already schema on the page?
This is important to know. If Seoella's schema is approved on the URL, Seoella treats its schema as the version to be used, and existing JSON-LD tags are replaced or removed. This also applies to schema from Yoast, Rank Math, or custom code. Read the full explanation in Seoella and existing schema.
Important
With the current implementation, Seoella does not complement your existing schema when Seoella's schema is approved. Seoella should then be regarded as the active schema implementation on the URL, not as an extra layer on top of existing JSON-LD tags.
Can the schema be validated?
Since Seoella's schema is delivered as JSON-LD on the page, it can be checked with the same tools as other structured data. Keep in mind that with the standard installation the schema is applied with JavaScript after page load, so check the rendered page rather than the raw source code. See JavaScript or server-side?.
Seoella and existing schema (Yoast, Rank Math, custom code)
When Seoella's schema is approved on a URL, it becomes the active schema implementation on the page. Existing JSON-LD tags may then be replaced or removed. This explains exactly what happens and how you control it.
What does Seoella do with existing JSON-LD?
If Seoella's schema is approved on the URL, the current implementation does the following:
Finds the first JSON-LD script tagThat is, the first <script type="application/ld+json"> on the page.
Replaces the content with Seoella's approved schemaThe existing JSON-LD data in that tag is replaced.
Removes additional JSON-LD script tagsOther JSON-LD tags on the page are removed to avoid duplicates.
Why does Seoella remove additional JSON-LD tags?
The purpose is to avoid having several schema implementations that overlap or compete with Seoella's approved schema at the same time. This also means you must be aware that other JSON-LD scripts may be removed while Seoella's schema is active.
Can Seoella overwrite schema from Yoast or Rank Math?
Yes, if Seoella's schema is approved on the same URL. Schema that is later added via, for example, Yoast, Rank Math, or manually can therefore be replaced or removed by Seoella.
Should I have both Seoella's schema and my own schema activated at the same time?
This is not recommended with the current implementation.
If Seoella's schema is approved, Seoella should be regarded as the active schema source on the URL.
If you instead want to control schema via the website, Yoast, Rank Math, or custom code, Seoella's schema should be revoked (unapprove) for that URL.
What do I do if I want to use my own schema later?
Revoke Seoella's schema on the relevant URLs. After that, the website's own schema implementation can be used. See Remove or revoke an approved change.
Does Seoella automatically complement my existing schema?
Not with the current implementation when Seoella's schema is approved. Seoella should then be regarded as the active schema implementation on the URL rather than as an extra layer on top of existing JSON-LD tags.
Summary
Seoella's schema on the URL
Result
Not approved
The website's own schema (Yoast, Rank Math, custom code) is used. Seoella does not touch the JSON-LD on the page.
Approved
Seoella's JSON-LD is active. The first JSON-LD tag is replaced, others are removed.
JavaScript or server-side?
Seoella can apply changes in two ways: with JavaScript in the visitor's browser (default) or server-side via the WordPress plugin. Here we explain the difference and when it matters.
Default installation: client-side JavaScript
In the default installation, changes are applied on the client side using JavaScript after the HTML page has loaded. The script loads asynchronously and is built so it doesn't block the page's initial rendering.
How often does Seoella try to apply the changes?
The current client implementation runs the DOM changes several times after page load:
immediately
after about 1 second
after about 3 seconds
after about 6 seconds
after about 10 seconds.
The purpose is mainly to be able to catch elements that load dynamically or via lazy loading.
Are the changes cached in the browser?
No. The default solution does not use localStorage or sessionStorage to save the applied DOM changes. The JavaScript process therefore also runs on new page loads, including for returning visitors.
WordPress: server-side
Via Seoella's WordPress plugin, it is possible to apply the changes server-side and output the optimized content directly in the HTML. The browser then receives the modified version right away, and JavaScript doesn't need to swap out the same content after rendering. See WordPress.
When does the choice matter?
Situation
Recommendation
You want to avoid visible content "flashing" when it's swapped out
The default installation with JavaScript. Google and Bing can render JavaScript.
Technical
Because the default installation changes the page after loading, the changes appear in the rendered DOM (Inspect element), not in the page's raw source code. With a server-side implementation, the changes are present directly in the HTML response.
Flash of original content
When visible content is swapped out with JavaScript, the visitor may briefly see the original version before Seoella's change is applied. Here we explain why, and how it can be avoided.
Can the visitor see the original content before Seoella changes it?
Yes, for visible DOM changes a brief flash can occur. The browser may first render the original content, after which Seoella's script applies the approved change.
Which changes are affected?
Only visible changes. The SEO elements Seoella normally changes are mainly located in the <head> (meta titles, meta descriptions, canonical, schema) or consist of metadata that doesn't affect the page's visual layout. There, no visible flash occurs.
Can the flash be avoided?
Yes, with WordPress. Via Seoella's WordPress plugin, the changes can be inserted server-side so the optimized content is written directly into the HTML. The browser then receives the modified version right away, and JavaScript doesn't need to swap out the same content after rendering. See WordPress.
Tip
If Seoella is used to change visible content, the change should be tested on the actual website, both for flashing and for any potential layout impact (CLS).
Performance and Core Web Vitals
Seoella's script loads asynchronously and, in Seoella's tests, has not shown any measurable negative impact on Core Web Vitals. Here we go through LCP, CLS, and what larger websites should monitor.
Does Seoella's script affect the website's loading time?
The script loads asynchronously. Seoella's current technical assessment is that the script has not shown any measurable negative impact on Core Web Vitals in the tests conducted. Seoella also describes the service as a solution with no performance downtime.
The script is hosted on S3 without a CDN. Is that a problem?
The script loads asynchronously and therefore does not block the initial HTML rendering the way a synchronous script would. Seoella has conducted performance tests with the solution and has not seen any significant negative impact on Core Web Vitals.
That said, it's reasonable for larger websites with strict performance requirements to continue monitoring, for example, LCP, INP, and CLS after installation.
Can Seoella affect LCP?
The script loads asynchronously and is built so it doesn't block the page's initial rendering.
Can Seoella affect CLS?
The SEO elements Seoella normally changes are mainly located in the <head> or consist of metadata that doesn't affect the page's visual layout. However, if Seoella is used to change visible content, the change should be tested on the actual website.
Note
The default solution does not save the DOM changes in the browser (no localStorage/sessionStorage), so the script runs on every page load. See JavaScript or server-side?.
Google, Bing, and AI search engines
Google and Bing can render JavaScript, but not all AI crawlers have the same rendering capabilities. Here we describe what that means for Seoella's JavaScript solution and when server-side implementation is especially relevant.
Can Google read Seoella's changes?
Yes. Google has rendering capabilities that can handle JavaScript.
Can Bing read Seoella's JavaScript changes?
Yes. Bingbot uses a modern rendering engine and can render JavaScript. The claim that Bing generally doesn't render JavaScript is outdated.
Can Seoella improve visibility in ChatGPT, Perplexity, and other AI services?
Seoella can improve the underlying SEO signals and the structured content that search engines and AI systems can use, but visibility in ChatGPT, Perplexity, or other AI services can never be guaranteed.
Is JavaScript a problem for AI search engines?
It depends on which crawler or AI service is used. Not all AI systems have the same JavaScript rendering as Google or Bing. That's why it's an advantage when important SEO elements are also available in server-rendered HTML. This is one of the reasons server-side implementation, where available, can be especially relevant.
Does that mean the JavaScript solution doesn't work for AI search?
No. It means you need to distinguish between different crawlers. Google and Bing can handle JavaScript. Other crawlers may have other limitations. For websites where maximum accessibility for various AI crawlers is a priority, server-side implementation is the most robust solution. See WordPress.
Crawler
JavaScript rendering
Works with the default installation?
Google
Yes
Yes
Bing
Yes, modern rendering engine
Yes
AI crawlers (ChatGPT, Perplexity, etc.)
Varies between services
Partially. Server-side is the most robust solution when maximum compatibility is required.
Keyword Rank Tracking follows the development of selected keywords over time and per geographic market, in the same platform as the recommendations and implementation.
Can Seoella track our Google rankings?
Yes. Seoella includes Keyword Rank Tracking to follow the development of selected keywords.
Can ranking be tracked over time?
Yes. Seoella shows historical ranking development so that changes and trends can be followed over time.
Can you track rankings from different geographic areas?
Yes. The rank tracking feature is location-based, making it possible to track keywords from different geographic markets.
How often is ranking data updated?
The update frequency can vary depending on the setup and plan. Some setups may use daily updates.
Why use Seoella's rank tracking if we already have Semrush or Ahrefs?
You can continue using other tools in parallel. The advantage of Seoella's rank tracking is mainly that ranking data is available in the same platform as the recommendations and implementation. This makes it easier to link an SEO change to the development of relevant keywords.
Note
An approved change does not affect ranking immediately. Google must first crawl and process the page. See When can we expect results?.
Create SEO articles with Seoella
Content Creation creates SEO-optimized articles based on, among other things, prioritized keywords, with configurable tone of voice, internal and external links, and metadata.
Can Seoella create SEO articles?
Yes. Content Creation can create SEO-optimized articles based on, among other things, prioritized keywords.
Can I control the tone of voice and brand voice?
Yes. You can configure, among other things, tone of voice, brand voice, and content style.
Can Seoella add internal links to articles?
Yes. Content Creation supports internal and external links within the content.
Does Seoella create metadata for the articles?
Yes. The articles are structured with, among other things, headings, links, and metadata.
Do we have to publish what is created?
No. Automation can be used when desired, but content can also be reviewed before publication. Read more in Publishing and scheduling articles.
Publishing and scheduling articles
Articles created in Content Creation can be reviewed manually or published automatically according to a publishing calendar in compatible setups.
Can articles be published automatically?
Yes. Content Creation supports scheduled and automated publishing in compatible setups. A publishing calendar can be used, and up to one article per day can be scheduled.
Do we have to automatically publish what is created?
No. Automation can be used when desired, but content can also be reviewed before publication.
Note
Seoella's current 90-day results guarantee has as one of its conditions that at least two posts are published per week. See When can we expect results?.
WordPress
Seoella works with WordPress via the default snippet, and with Seoella's WordPress plugin, changes can also be applied server-side instead of via JavaScript after page load.
Does Seoella work with WordPress?
Yes. Seoella can be used with WordPress.
Two ways to run Seoella on WordPress
Code snippet in <head> (default)
WordPress plugin (server-side)
How changes are applied
With JavaScript after page load
Server-side, directly in the HTML response
Flash of visible content
May occur
Avoided
Changes are present in the raw source code
No, in the rendered DOM
Yes
Crawlers with limited JavaScript rendering
May miss changes
See the changes directly
When should you choose server-side?
Server-side is mainly relevant for websites that want to avoid changes being applied only after rendering, for example to avoid a flash of visible content or to ensure important SEO elements are present in server-rendered HTML for crawlers with limited JavaScript rendering. See Google, Bing, and AI search engines.
Yoast and Rank Math
If Seoella's schema is approved on a URL, schema from Yoast or Rank Math can be replaced or removed on that URL. If you want Yoast or Rank Math to control the schema, leave Seoella's schema recommendation unapproved (or revoke it) on the URLs in question. See Seoella and existing schema.
Shopify, Wix, custom-built sites, and other CMS platforms
Seoella's default solution is built to work independently of CMS, as long as the code snippet can be installed in the website's <head>.
Does Seoella work with Shopify, Wix, and other CMS platforms?
Seoella's default solution is built to work independently of CMS, as long as the code snippet can be installed. Seoella.com mentions, among others, WordPress, Shopify, and Wix as examples of platforms where the solution can be used.
Does Seoella work on a custom-built website?
Yes, in most cases. If the website allows Seoella's code snippet to be installed, the platform can also be used on custom-built websites.
What's different from WordPress?
The server-side implementation via plugin is available for WordPress. On other platforms, the default installation is used, where changes are applied with JavaScript after page load. See JavaScript or server-side?.
The installation steps are the same regardless of platform. See Install Seoella.
When can we expect results?
Seoella can make a change live immediately, but how quickly Google reacts depends on the website, the keyword, the competition, and many other factors. Here we describe what governs the timeline and the conditions of Seoella's results guarantee.
How quickly can you expect SEO results?
There is no exact time period that applies to all websites. Seoella can make the change live immediately, but how quickly Google crawls, indexes, and reacts to the change depends on the website, the keyword, the competition, and many other factors.
Does an approved change mean Google changes immediately?
No. The change on the website can happen immediately, but Google must still crawl and process the page before the change can affect the search results.
90-day results guarantee
Seoella currently communicates a 90-day results guarantee with specific conditions, including that:
the service is installed on the website for the entire period
at least 80 percent of the recommendations are approved within 14 days of upgrading to a paid plan
at least two posts are published per week.
Note
The full terms of the guarantee are available at seoella.com.
How to measure the impact in Google, Bing, and AI search
The impact of Seoella is mainly tracked via organic traffic per search engine in Analytics, ranking changes, and landing pages that receive organic traffic. External tools are used for AI search.
What is measured when talking about improved visibility?
Mainly:
organic traffic per search engine in Analytics
changes in ranking
landing pages that receive organic traffic
development before and after implementation.
Has Seoella seen any impact from Bing?
In Seoella's own analyses, organic traffic from Bing has developed positively on several of the websites where Seoella has been activated, with a development that in the tests resembled what has been seen from Google. This has mainly been tracked via Analytics.
How is AI visibility measured?
Among other things, through external tools such as Semrush's AI Visibility data. This can, for example, be used to track:
how often a brand is mentioned
which pages appear
which questions or topics the brand is associated with
With Keyword Rank Tracking, ranking data is available in the same platform as the recommendations and implementation, making it easier to link an SEO change to the development of relevant keywords. See Tracking your Google rankings.
Managing multiple clients' websites
Seoella has a dedicated agency setup where multiple client websites can be managed and optimizations deployed from the same system.
Is Seoella built for SEO agencies?
Yes. Seoella has a dedicated agency setup where multiple client websites can be managed and optimizations deployed from the same system.
Can an agency manage multiple clients' websites?
Yes. The platform is built to scale SEO work across multiple websites and clients.
What's the main difference compared to a traditional SEO audit tool?
A traditional audit tool often identifies what should be changed. Seoella's main difference is that the recommendation can also be implemented from the platform after approval, without each change first having to be sent as a development ticket to the client's developer.
Tip
The same precautionary principle applies per client: start with a limited number of categories, verify, and expand. Be especially clear with clients who already have schema via Yoast, Rank Math, or their own code. See Seoella and existing schema.
My changes aren't showing up
An approved change not showing up is usually due to where you're looking, the recommendation not being approved, or Google not having crawled the page yet. Go through the points below in order.
1. Is the recommendation approved?
If a recommendation isn't approved, Seoella doesn't affect the current element. Check the status in Seoella's interface for the current URL.
2. Are you looking at the source code or the rendered page?
In the standard installation, changes are applied with JavaScript after the HTML page has loaded. They therefore don't appear in the page's raw source code, but in the rendered DOM. Use your browser's developer tools (Inspect Element) instead of view source.
With the WordPress plugin's server-side mode, the changes are present directly in the HTML response. See WordPress.
3. Is the element loaded dynamically?
The script runs the DOM changes several times after page load: immediately, plus after roughly 1, 3, 6, and 10 seconds, to catch elements that load dynamically or via lazy loading. Wait a few seconds after page load before checking.
4. Is the code snippet installed on the page?
Check that Seoella's code snippet is present in the <head> of the current page, not just the homepage. See Installing Seoella.
5. Are you waiting on Google?
The change on the website can take effect immediately, but Google must crawl and process the page before the change can affect the search result. The search result still showing the old value doesn't mean the change isn't live. See When can we expect results?.
6. Are the CMS and Seoella trying to control the same element?
Avoid having both the CMS and Seoella try to control the same element at the same time when Seoella's version is approved. Decide which source should own the element. See Can Seoella harm our existing SEO?.
Still having issues?
Contact hello@seoella.com and specify the current URL and which recommendation it concerns.
My existing schema disappeared or changed
If schema from Yoast, Rank Math, or your own code has been replaced or disappeared, it's most likely because Seoella's schema is approved on the current URL. This is expected behavior and can be changed.
Why did this happen?
When Seoella's schema is approved on a URL, Seoella treats its schema as the version to be used. The implementation finds the first JSON-LD script tag, replaces the content with Seoella's approved schema, and removes additional JSON-LD script tags on the page to avoid duplicates. Read the full explanation in Seoella and existing schema.
Check the pageAfter that, the website's own schema implementation can be used on those URLs. Check the rendered page.
Choose a source per URLYou can use Seoella's schema on some URLs and your own schema on others. Only approve Seoella's schema where you want to use it.
Important
Having both Seoella's schema and your own schema enabled at the same time on the same URL is not recommended with the current implementation. Schema later added via Yoast, Rank Math, or manually can be replaced or removed as long as Seoella's schema is approved on the URL.
Frequently asked troubleshooting questions
Short answers to questions that often come up when something doesn't look as expected.
My canonical tags have changed. Why?
Seoella only changes the canonical if a canonical recommendation is approved on the URL. Check the status and revoke the recommendation if you want to use your own canonical. See How canonical tags work in Seoella.
The content "flashes" and gets swapped shortly after the page loads
This is a flash of the original content: the browser first renders the original, and Seoella's script then applies the approved change. This only applies to visible DOM changes. With the WordPress plugin, changes can be made server-side so the flash is avoided. See Flash of original content.
The change appears in the browser but not in "view source"
This is expected with the standard installation, since the changes are applied with JavaScript after page load. See JavaScript or server-side?.
I approved a change but the ranking hasn't changed
Google must crawl and process the page before the change can affect the search result, and how quickly that happens depends on the website, the keyword, and the competition. See When can we expect results?.
I revoked a change. Why does Google still show Seoella's version?
For the same reason: the search result only updates once Google has crawled and processed the page again. On the website itself, Seoella should no longer apply the change.
Does the script seem to affect load time?
The script loads asynchronously, and Seoella's tests haven't shown any significant negative impact on Core Web Vitals. Larger websites with strict performance requirements should still monitor LCP, INP, and CLS after installation. See Performance and Core Web Vitals.