Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Dynamically loaded content is generally hard to get right from an SEO perspective. Your description is a little confusing, but I think I have an idea of what you're looking for.</p> <p>First of all, there are mainly two ways with which Google finds out about pages on your site:</p> <ul> <li>A Sitemap (Google likes XML sitemaps) - A file that tells Google every page on your site to index</li> <li>Links - Google will follow any internal link on pages it tries to index unless they are marked with <code>rel="nofollow"</code></li> <li>There's also links in and some other stuff, but for the purposes of this explanation...lets ignore those.</li> </ul> <p>Anyway, unless you're explicitly telling Google that <code>website.com/single.php?blog_no=12</code> exists, it's going to have a hard time finding it. To be honest, I'm not sure how Google will handle something like <code>href="12"</code>, it may try to follow that link to <code>website.com/12</code> which may effect your ranking if there is nothing there. So in the end, you might want to add <code>rel="nofollow"</code> to your AJAX trigger links.</p> <p>A good way to handle AJAX and dynamically loaded content is to make sure fallbacks are in place, for example if you have something like <code>href="single/12</code> set up to load some content with AJAX, you should also have a fallback page that doesn't use JS/AJAX. This ensures that both search engine bots, and users without Javascript can see that content if it otherwise wouldn't have been visible anywhere else.</p> <p>Last small tidbit, if you test your links on something like <a href="http://www.dnsqueries.com/en/googlebot_simulator.php" rel="nofollow">http://www.dnsqueries.com/en/googlebot_simulator.php</a> and they turn up with errors, or blank pages (search engine bots don't use javascript) you should nofollow those links, or setup fallback pages</p> <p>Nevermind...this is the last thing. You should go a couple steps further with your htaccess rewrite to make your URLs completely clean of query strings. For example <code>website.com/single/blog/12</code> is better than <code>website.com/single.php?blog_no=12</code> for both SEO and users.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload