Welcome to the Q&A Forum

It's a bug from Google's end, you need to contact GMB support to fix this.

In my experience, Google quite often see this (rightly or wrongly) as an illegitimate attempt to increase your search footprint. Quite often some listings get banned, denied, removed, or increased scrutiny is put on your original listing Google really wants serrate listings for separate businesses, not separate listings for different services. That's why it's called Google My Business and not Google My Service. The core remit of the platform is to list businesses, not fragmented services. To those who try to derail this, sometimes it can work pretty well - but usually (in the end) it causes more problems than it solves You could label your services as different businesses and give them different internal addresses (e.g: Unit 1, Unit 2 etc). If that seems really inaccurate, then it probably says that your attempt to diversify online in jumping the gun a little (and Google may not embrace it)

You will want to use hreflang, either in the pages or in the sitemaps of the two sites. I'm assuming that you want the pages from the first site to rank for searches in Australia, and the second site's pages to rank in US. And hreflang tags are how you will communicate that desire to the search engines. The AU site should have a self-referencing hreflang tag for "en-AU" and another hreflang tag for "en-US" pointing to the equivalent page on the sister site. You may also want to include an x-default tag as well. The US site should have a self-referencing hreflang tag for "en-US" and another hreflang tag for "en-AU" pointing to the equivalent page on the sister site. You may also want to include an x-default tag as well. And, you also probably want to geographically target the two sites (or at least one of them) in Search Console settings. Lastly, in case a visitor lands on the wrong site (the search engines don't always obey our directives), you will want some way to inform the visitor that there is a "more appropriate" site. This can be a modal dialog based on geo-ip, or it can be just part of the site design, or however makes sense for your business.

You could always force trailing slashes instead of removing all trailing slashes. What you really want to establish, is which structure has been linked to more often (internally and externally). A 301 redirect, even a deeper more complex rule - is seldom the answer in isolation. What are you going to do (for example) when you implement this, then you realise most of the internal links use the opposite structure to the one which you picked, and then all your internal redirects get pushed through 301s and your page-speed scores go down? What you have to do is crawl the site now, in advance - and work out the internal structure. Spend a lot of time on it, days if you have to, get to grips with the nuts and bolts of it. Figure out which structure most internal/external links utilise and then support it Likely you will need a more complex rule than 'force all' or 'strip all' trailing slashes. It may be the case that most pages contain child URLs or sub-pages, so you decide to force the railing slash (as traditionally that denotes further layers underneath). But then you'll realise you have embedded images in some pages with URLs ending in ".jpg" or ".png". With those, they're files (hence the file extension at the end of the URL) so with those you'd usually want to strip the slash instead of forcing it At that point you'd have to write something that said, force trailing slash unless the URL ends with a file extension, in which case always remove the slash (or similar) Picking the right structural format for any site usually takes a while and involves quite a bit of research. It's a variable answer, depending upon the build of the site in question - and how it has been linked to externally, from across the web I certainly think, that too many people use the canonical tag as a 'cop out' for not creating a unified, strong, powerful on-site architecture. I would say do stick with the 301s and consolidate your site architecture, but do some crawling and backlink audits - really do it properly, instead of just taking someone's 'one-liner' answer online. Here at Moz Q&A, there are a lot of people who really know their stuff! But there's no substitute for your own research and data If you're aiming for a specific architecture and have been told it could break the site, ask why. Try and get exceptions worked into your recommendations which flip the opposite way -  i.e: "always strip the trailing slash, except in X situation where it would break the site. In X situation always force the trailing slash instead" Your ultimate aim is to make each page accessible from just one URL (except where parameters come into play, that's another kettle of fish to be handled separately). You don't have to have EVERYTHING on the site one way or the other in 'absolute' terms. If some URLs have to force trailing slash whilst others remove it, fine. The point is to get them all locked down to one accessible format, but you can have varied controlled architectures inside of one website

hi, You can try these tools: https://developers.google.com/speed/pagespeed/insights/ https://www.pingdom.com/ https://gtmetrix.com/ https://www.dareboost.com/en regards

As Alex & MrWhippy said, if structure urls --regex is best. If you can't use regex and have to redirect that many, will impact speed of the site. You can do it w/the include directive in httpd.conf.  Good luck.

Hi  brandonegroup - Have you thought about posting this question in the Magento forums? Christy

I think it would be something like: <code>RewriteEngine On RewriteCond %{HTTPS} off RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] This would go in your .htaccess file, you should be sure to edit the file via FTP so that if you break it, you can restore the old version and fix the site in seconds (keep a backup of the old .htaccess file) If you are on a windows-based server you'd need the equivalent rule for your web.config file as IIS doesn't use .htaccess For most sites, you have a .htaccess file and it sits in the root of your FTP (the same place that your primary index.php file lives, where robots.txt and sitemap.xml also usually reside)</code>

Hello there! I might need some clarification here. The screenshots look to me like they are extracted from a Google Business Profile, in which case, they are stemming directly from the reviews customers leave you on Google. If I'm misunderstanding, would you mind taking a screenshot of the whole search engine results page so I can better understand the context of where you are hoping your reviews will appear? Thanks and I'll check back on this thread.