Hi @pstidsen,
It is currently not possible to distinguish between different domains within one WordPress setup. I’ve always understood that this is not ideal for SEO, as the domain authority gets split over several domains. But I might be wrong! It would be great if you can share your view on this.
You can add your feature request here: https://burst-statistics.com/feature-requests/
Our roadmap is partly shaped by feature requests with many upvotes.
Hi Rogier,
I have had the exact same concern. Therefore, we are using the option in WPML to use completely different domains for each language (different TLD for each language). That must rule out any SEO concern. However, we will still love to measure the traffic including the domain directly in Burst. It is easily to identify traffic when the slugs are spelled different in different languages. However, e.g. “contact”/”kontakt” or “shop” is the same in many languages. Likewise, visits at the home page are bundled as “/” for all languages.
The second-best option, with a significant SEO-risk, AFAIK, is to use .com (or similar non-country TLD) with each language in a folder or subdomain. People using this setup (which is pretty common) will also benefit from traffic measuring with domain.
Best Regards,
Peter
Hi Peter, what you said about domains and subfolders surprised me a bit, so I double checked with chatgpt, and I got this answer:
Google has confirmed that both subdomains and subfolders work fine for SEO — there’s no significant SEO risk in using folders or subdomains as long as hreflang and structure are set up correctly. Many SEOs observe that subfolders often perform better in practice because domain authority is consolidated, but that’s not an official Google rule.
That said, we’ll think about how this could be handled in the plugin, and discuss adding it to the roadmap.
I’d like to invite you to add this as a feature request here:
https://burst-statistics.com/feature-requests/
Then we can also see how many votes it gets, which would tell us a bit about broader interest.
Hi Rogier,
Here’s a feature request open for voting (and implementing ;-)): https://burst-statistics.com/feature-requests/add-option-to-track-by-full-domain/
Best Regards,
Peter
Thanks for your input, we’ll discuss how this could be implemented. A question about a possible implementation: We could add a “domain” column to the settings, and a domain filter in the advanced filters. Would that suit your purposes?
Yes, indeed. That sounds like a perfect implementation. I can imagine it would work if the domain either was a separate column or just included in the Page URL column.
As far as I can see, the database tables do not contain the domain part of the URL’s at the moment, which I guess will mean that only traffic measured after an implementation will be able to be filtered. That’s of course OK!
Hi @pstidsen,
I have a test version with this feature, if you’re interested, please contact us at support(at)burst-statistics.com.
