spectrum
Forum Replies Created
-
Posts
-
Thanks Guust
I should have thought of doing that – it’s working now.
Am I correct in assuming that the breadcrumb text for Location can only be changed through the translation file?
This reply has been marked as private.Yes, I think an additional variable like that would be a useful way to give each listing a unique title and that should bring some SEO benefits
Many thanks
Yes, that’s the issue. I don’t particularly want to be tinkering with the business name in each instance.
The ideal solution for me would be to be able to add another differentiating variable such as street address, or a recognisable location such as shopping mall name, cross streets, neighbourhood etc
I’m probably missing some thing, but if, for example, my title is set as
%%title%% in %%location%%am I not still going to end up with lots of pages with identical titles. eg Starbucks in London
Siofan
Yes, I’m aware of the Franchise Manager addon but I haven’t seen it in operation. I can see the huge benefits of being able to have all of those businesses tied to a main listing, but I’m not sure it’s what I need. For many reasons, I still need to be able to individually adjust and optimise individual locations almost as though they were unrelated businesses.
At this stage, I’m tying to get a sense of whether what I’m asking for is feasibie, I’m surprised it’s not something more people are asking for (i.e. the ability to tailor titles, descriptions in more granular detail).
If I have to hire a developer to modify, I’m happy to do that – just trying to understand how complex it might be to accomplish. I was thinking of some way to just pick up the street address line as a variable that could be used in the title and description.
Many thanks
I thought that might be the case.
I don’t know anything about Yoast, but I wonder whether it could be set up in some way to rewrite the URLs with the shortened country slug?
If not, maybe I’ll have to use the jobs section to find someone who can modify the code in some way.
Many thanks
This reply has been marked as private.This reply has been marked as private.Many thanks. I also noted the following on the Google Geo Developers Blog:
Future Changes to Geocoding API
We plan to roll out an update to the Geocoding API at the end of November 2016 that will increase the difference between Geocoding and Places performance for ambiguous and unambiguous queries. This change will improve the quality of Geocoding results for unambiguous queries, but will be more likely to return ZERO_RESULTS for ambiguous or incomplete queries where the Geocoding API was unable to find a high quality result.
I venture that this could become a growing issue given that many end users will be putting ambiguous or incomplete locations in the search box.
Is using the Google Places API with autocomplete a potentially better solution here and would that be a big job to implement?
Yes, it’s quite frustrating because it’s creating a bit of a hit-and-miss experience for the user. Most users will not know to experiment with dropping the street number to see it it works.
If I enter 500 California Street, San Francisco (which is literally a block away from 555) it finds results without a problem. Seems to me that the Google API isn’t happy with something, but without seeing the underlying detail, it’s hard to figure out what the problem is.
When I run the address through other geocoding services that use the Google API it can geocode the address with no problem, so the actual address is not the issue.
Hope we can figure this one out!
Thanks
Guust
Adding that CSS sorted the problem.
Thanks
Kiran
That’s fixed now – many thanks.
This reply has been marked as private.This reply has been marked as private.
