Mobile app version of vmapp.org
Login or Join
Lengel546

: SEO on AJAX based search site I'm building a website which is basically a simple 1 page with a search box, and AJAX'd search results displayed in a table. I'm having trouble finding out the

@Lengel546

Posted in: #Ajax #CrawlableAjax #Googlebot #Seo #WebCrawlers

I'm building a website which is basically a simple 1 page with a search box, and AJAX'd search results displayed in a table.

I'm having trouble finding out the correct information about crawlability and indexing with this.

An article on SearchEngineLand (March 5, 2015) notes that:


Google May Discontinue Its AJAX Crawlable Guidelines


With a suggestion that it no longer needs to offer this as it is capable of crawling an AJAX'd site.

What I'm having difficulty with is:


Whether I should try and make my AJAX search results crawlable, and if so whether I need to do anything to make my site and the asynchronous search results table crawlable
Or whether I should just disallow all indexing of search results, and have individual pages for each search result item instead, that can be indexed separately and included in a sitemap - as explained here.


Some real examples of option 1 and 2:


Build a (somehow) crawlable AJAX search result table so a page with a search for "Foo Bar" displaying a results table of items relating to "Foo Bar" will be indexed.
Or a crawl blocked search result table with results for "Foo Bar", each item in the results table will be linked to an individual page for that item e.g. foo-bar-a.html, foo-bar-d.html etc. These pages are crawlable and submitted in sitemap.


Option 1 I beleive could be limiting in the future, and I have the trouble of finding a way to make the AJAX search function and results crawlable. I think it also throws up a duplicate content issue.

Option 2 gives room for expanding content on these separate pages and hopefully ranking better for each result, but of course involves a lot more work. I can imagine also a problem with duplicate or thin content on these individual pages as there would be very little data to begin with.

What's people's opinion on the best option here?

I hope that all makes sense.

10.02% popularity Vote Up Vote Down


Login to follow query

More posts by @Lengel546

2 Comments

Sorted by latest first Latest Oldest Best

 

@Nimeshi995

Apart from providing your results via the ajax method, you could also interpret the search query from the URL parameters or URL structure (via apache aliasmatch ?).

e.g example.com/zoo.php?q=unicorns or example.com/zoo/jellytiger

and then return a page with the data already in the html, as if a user would have just typed unicorns or jellytiger in the search box.

This has the advantage that you or another website could directly link to a specific content, but also that you can make a sitemap that you can submit to the search engines.

10% popularity Vote Up Vote Down


 

@Heady270

Site search and search results shoud never be crawlable, regardless of whether they are AJAX or not. See: Matt Cutts: search results in search results. Google penalizes sites that try to get their search results indexed.

Googlebot is now starting to execute JavaScript and index any text that gets written into the page. I have a random password generator website and I found some of the JavaScript generated passwords indexed by Google recently. Google is getting better at indexing the page as the user sees it rather than just what it can find in the initial page source.

Google has also said that using AJAX with push state is a great way to make a site fully crawlable but still powered by AJAX. Moz.com has a full example tutorial for doing it:


The initial page load loads the full page including all content inline
Clicks load new content into just the content area and use push state to change the URL
The back button uses pop state

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme