Google: Schema Markup Does Not Guarantee Sitelinks Search Box

Sep 8, 2014 - 8:57 am 3 by
Filed Under Google

Google Sitelinks Search Box

On Friday, we reported on the new Google Sitelinks Search box - read that first if you missed it.

One new tidbit that I am glad Google's Pierre Far confirmed and I am incredibly upset the SEO space assumed incorrectly (at least some) was that adding the scheme markup 100% does not guarantee your site for having the new Sitelinks Searchbox feature.

Pierre Far from Google explained on Google+ minutes ago:

The question is: would adding the schema.org markup guarantee a site getting the search box?

The answer is no. It's a bit more nuanced (and clever) than that.

Pierre also shared another tidbit:

Bonus question on my previous G+ thread: Will adding a tracking parameter to URL pattern upset this at all?

Answer: not at all! But, as you're adding more complexity to your URL pattern, double and triple check it works correctly.

Finally, I do not believe Google won't show the search box if you do not add the schema, Google will still show it if they want to. The only thing it won't automatically do is redirect the search results to your site. Update, Google confirmed this.

Forum discussion at Google+.

 

Popular Categories

The Pulse of the search community

Search Video Recaps

 
Video Details More Videos Subscribe to Videos

Most Recent Articles

Search Forum Recap

Daily Search Forum Recap: July 10, 2025

Jul 10, 2025 - 10:00 am
Google Updates

Google June 2025 Core Update Leading To Some Partial HCU Recoveries

Jul 10, 2025 - 7:51 am
Google Search Engine Optimization

Google Search Console Performance Report Average Position Bug?

Jul 10, 2025 - 7:41 am
Google Ads

Google Search Ads People Also Consider Carousel Format

Jul 10, 2025 - 7:31 am
Google Maps

Google Business Profiles Drops Utility Bill As Evidence For Appeal

Jul 10, 2025 - 7:21 am
Google

Google AI Mode Comes To Circle to Search and Lens

Jul 10, 2025 - 7:11 am
Previous Story: Google's Matt Cutts Migrates Blog To HTTPS But Uses 302 Redirects