indexes

In PG, you can use functions to create indexes and when the function is used in a where clause that index will be used.

Showing that it gets indexes does not show how well it would rank wrt normally visible text, though.

My main problem with quality of life indexes is they tend to overvalue income equality.

If you store transactional information in your indexes as well (some do, some don't) the relative space consumption is even worse.

Something that indexes the entire web and answers queries about which links overlay this document.

If you remove the indexes and render the information difficult to find, its not that much different from removing the information altogether.

In the more common cases, you get indexes on foreign keys for free.

Further, Google probably indexes tons of images which are infringing on someone's copyright and you can view these right in their search results.

Sure, it indexes the text, but that has no bearing on SEO.

You can use functions to create constraints, unique indexes and even notify outside process that are listening of changes in the database with pubsub.

The point of the extension is to index what I visit to make it easy to search - it's only useful if it indexes the majority of the content I visit.

The optimiser seems to get a bit stuck on understanding what indexes to use for queries that involve multiple joins or more complex data structures.

From the article, "China's main stock indexes had more than doubled over the year to mid-June,"

Google can index (and indexes) hidden text and dynamically inserted text." Then concludes the entire thing with something completely unrelated: "If content is relavant [sic] to Your website, You won't get penalty from google.