Examine is not a crawler but an indexer. The way that it is configured in Umbraco is to create an index of the raw published content, and not necessarily how you use that content. So it does not index the rendered page but instead based on the back office node structure and the configuration rules provided in the /config files.
If you are wanting to index the rendered output then you will need to create a custom index stuffed with the content that you want it to index. As Examine is not necessarily an Umbraco technology you can write your own custom indexing providers to index the page as it is rendered.
Examine crawler
Hi,
Is there any special reason the crawler is just crawling the nodes instead the website just like google would crawl it ?
I'm asking because as the crawler works now it does not work on content on Macros or other custom data.
Has anybody found a solution to make it crawl the content inside macros ?
Thanks in advance.
Examine is not a crawler but an indexer. The way that it is configured in Umbraco is to create an index of the raw published content, and not necessarily how you use that content. So it does not index the rendered page but instead based on the back office node structure and the configuration rules provided in the /config files.
If you are wanting to index the rendered output then you will need to create a custom index stuffed with the content that you want it to index. As Examine is not necessarily an Umbraco technology you can write your own custom indexing providers to index the page as it is rendered.
is working on a reply...