Forum Moderators: phranque
e.g. A site which provides information on widgets has 500 pages indexed by SE's. The site also has a lookup database which users can search to find out about Blue Widgets, Habanero Widgets, Aquatic Widgets and stuff. In total there are 5,000 different widgets where data can be viewed.
That works well but SE's don't get to know about the meat in the database. All they index are the articles about widgets - they never get to extract the 5,000 DB records.
So what if static content was created which is not really for users to read, but so that SE's will think the site is really big and clearly on theme?
Say, extract info about each widget and create thousands of pages correctly titled, H1'd, and with some useful human readable info:
--------------------------------------------
blue_widgets.html
<title>blue widgets....
.
.
Blue Widgets are mostly found in North America. They are not particularily tasty and are often used for decoration
habanero_widgets.html
<title...
.
.
Habanero Widgets are one very hot widgets and originate from Mexico. They can be used to compliment beer and potato chips.
----------------
I wouldn't consider this to be spammy. The purpose is to show SE's that the database is huge, and thus the site could be a leading authority on widgets. It will be good for users arriving at these static pages as they can get a brief intro about the widgets before using the full database search box.
Good or bad idea?
I could put a link to 'full list of widgets' from the sitemap page and hopefully the SE's will follow the links.
I was thinking of something like:
"full list of widgets ->"
and then that to call full_widgets.html page which contains:
Click any of the links below to read about the individual widget:
blue widgets
green widgets
.
.
.
flat leafed widgets
Each link then calls it's own full text page.
