Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify and geocode Salesforce addresses

Highlighter

Colors, renames or hides Salesforce fields

List Browse

Browse Salesforce records without list clicking

Get started

Install, configure and roll out a TAF package.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article per task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case and a person reads it.

Open a support case

The fastest route to an answer

Give us access

Let us sign in and see the problem

Support home

Guides, release notes and the case form

Troubleshooting

Search by the error text you see

Documentation

Written for admins, not for developers.

Implementation guides

Guides for all four apps are ready.

How-to articles

One task per article

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo
Address Verification · How-to

Improve checks with Google Search

How to do it in Address Verification, one step at a time.

Last updated 11 Oct 2026

Optional. Not available at this time.

Not available at this time

This problem comes from a change on Google's side. In 2025, Google changed its search pages so that they need JavaScript. Address Verification can no longer read the Did You Mean? text from them.

With Use Google Search on, Verify fails for each address that Smarty cannot verify. The record gets no result, and the check uses two lookups.

TAF is adapting Address Verification to Google's change and is working on a fix. Until the fix is out, leave Use Google Search off. The Address Verification change log will announce the fix. See also Verify fails with Unexpected character.

Google Search helps with an address that Smarty marks as bad, for example a street spelled in the local language.

Address Verification first sends the address to Smarty. If Smarty marks it as bad, the app searches Google for the address. If Google offers another spelling with Did You Mean?, the app sends that spelling to Smarty. When that check works, the address is verified. When it fails, the Footnotes say so.

Smarty fixes small spelling mistakes itself, so most addresses never go to Google.

A second lookup

The check of the Google spelling uses a second lookup.

Only for a click on Verify

Google Search works only when a user clicks a Verify action. It does not work in scheduled batch jobs.

  1. Add Google as a remote site.

    Open Setup. In the Quick Find box, type Remote Site Settings. Click Remote Site Settings. Click New Remote Site.

    FieldValue
    Remote Site NameAny name, for example Google_Search
    Remote Site URLhttp://www.google.com
    ActiveTicked

    Click Save.

  2. On the Options tab, tick Use Google Search. Click Save Settings.

    A message reads Setting is Saved Successfully.

  3. Verify a test record with a hard address.

    Open a record whose address Smarty cannot verify. A small spelling mistake is not enough. Smarty fixes it itself, and the Footnotes end with Verified by SmartyStreets.

    Click the Verify action. Read the Return Code and Footnotes fields of that address. The check uses one or two lookups.

    At this time the check fails with Verification Failed. Untick Use Google Search again. See Verify fails with Unexpected character.

Applies to

Address Verification 7.3.x. These steps come from the tested Address Verification implementation guide, where they sit with the steps before and after them.

Was this helpful?

Related

Support

Still stuck?

Open a case and paste the exact error text. A person reads every case.