Google robots.txt Tester

[SanfordWhiteman · Accepted solution]

You haven't changed your form embed code. You need to change both references to //app-ab13.marketo.com to your now-SSL-protected Marketo LP domain.

[Pete_Jones]

Well, the embed code in the Marketo system is the exact same. Do I need to recreate the form to get the new code??

[SanfordWhiteman]

The code offered in the UI won't change. You must make those 2 edits to the domain.

[Pete_Jones]

Thank you Sanford. But, forgive me, how do I figure out what our new ssl domain is if the system is populating the above domain with new forms, etc?

[SanfordWhiteman]

It's your primary LP domain! (In Admin.)

[Pete_Jones]

Our primary lp domain is https://go.guideone.com. If I hover over our Marketing Activities icon in the Marketo main screen the https://app-ab13.marketo.com/#MA domain pops up in the lower left for the Marketing Activities section. That must still be our domain.

[SanfordWhiteman]

... the https://app-ab13.marketo.com/#MA domain pops up in the lower left for the Marketing Activities section. That must still be our domain.

Nope, the URL of the Marketo UI will not change in any case. You must change the embed code as recommended.

[Pete_Jones]

Okay. Thanks for hanging with me Sanford. I have changed the domain in the code to the go.guideone.com domain I stated above. The form continues to populate, so that is a good thing. But, the first render I did with the Google Search Console still showed the old form domain and stated it was blocked. Guess I'll try it again tomorrow to see if they're able to see the first domain and ideally actually see the form when the robots crawl.

[SanfordWhiteman]

Yes, wait for the next crawl.

[Pete_Jones]

Wonderful! It worked. Thanks so much Sanford!