Local SEO - street address rearranging to inaccurate format upon validation

[4e-blewis]

Entered street address reads 4435 Sunbeam Rd. Validation button reveals an accurate option. Once validation option is chosen, the plugin/extension rearranges it in the field to read Sunbeam Rd 4435 ... placing the house/building # behind the street/road name. I'm assuming this is a bug

[sybrew]

Hi @4e-blewis

This inaccuracy happens when no house/apartment number is provided. Some combinations work better than others when it's omitted.

From the changelog:

Our Geocoding services now accepts street entries without numbers, the effectiveness might vary based on [the] secondary input.

Ignore the above; I wrongly read your question.

This is the default behavior because we can't know the structure beforehand. So, the plugin places the number behind the street name: https://github.com/sybrew/The-SEO-Framework-Extension-Manager/blob/master/lib/js/tsfem-form.js#L536

You can rewrite the validated street address, so it isn't a big issue; either arrangement should be correctly interpreted too.

I'll see if I can get the "correct" format, regardless, in a future update.

[4e-blewis]

Thanks for the quick response. Understood, but in this scenario, the house/apartment number was provided, the validation tool offered the same address, and it rearranged in the field after selecting the validation tool’s recommendation. On Jul 6, 2018, 4:37 PM -0400, Sybre Waaijer [email protected], wrote:

Hi @4e-blewis This inaccuracy happens when no house/apartment number is provided. Some combinations work better than others when it's omitted. From the changelog:

Our Geocoding services now accepts street entries without numbers, the effectiveness might vary based on [the] secondary input. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[sybrew]

Hi @4e-blewis,

I've updated my previous reply; I read your inquiry wrong.

[4e-blewis]

Thank you for your quick responses & TSF

[sybrew]

No problem! I'm keeping this open as I want to investigate whether we can get the "correct" format. I'll lock the thread for new comments to prevent your email inbox getting filled.

[sybrew]

The formatted address seems to support the statements:

Unfortunately, we're not acquiring any other information that suggests the number/name order. We can't rely on the formatted address, as it's extremely diverse across the globe, and we must deliver the format in parts.

Now, I could discriminate (as most users are in the USA), by placing it in front, but that doesn't solve the issue for everyone.

When you notice mistakes, I suggest manually correcting the auto-filled data. However, the format shouldn't matter as it's interpretable and reversible by Google. So, this is a non-issue.

I'm marking this as "wont-fix" until further notice. I'll reinvestigate when the API gets updated.