Search results include HTML classnames

  • Resolved DODO Internet

    (@studioviv)


    6 days, 11 hours ago

    Hello,

    We noticed that Ajax Search Lite also indexes HTML elements and their classnames inside the post content. Because of this, searches return posts that do not contain the searched word in the visible text, but only inside an HTML classname.

    For example, searching for “Pointer” returns posts where this word appears only in a classname within the HTML markup.

    Is there a way to disable indexing of HTML tags and attributes, so the search engine only looks at the actual text content?

    Thank you in advance.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Ernest Marcinko

    (@ernestmarcinko)

    6 days, 11 hours ago

    Hi,

    I’m afraid it is not possible. This Lite version searches the post contents database directly (it doesn’t index them separately). If the content contains the HTML rendered and is stored in the database, then for SQL queries it is simply text content.

    All the best,
    Ernest

    Thread Starter DODO Internet

    (@studioviv)

    6 days, 10 hours ago

    Hello @ernestmarcinko ,

    Thank you for the clarification.

    Just to confirm: since the Lite version searches the raw post content stored in the database, it will always index HTML tags and classnames if they exist inside the post content, correct?

    In that case, do you have any recommended approach to prevent HTML attributes from affecting search results? For example:
    – stripping HTML before indexing
    – filtering the content before the SQL query
    – or using a hook to preprocess the content

    If this is possible in the Pro version, please let me know.

    Thanks again for your help.

    Plugin Support Ernest Marcinko

    (@ernestmarcinko)

    6 days, 9 hours ago

    Hi,

    The Lite version does not have a separate index to do that unfortuantely.

    Hooks in this case wouldn’t work, because the SQL content has to be modified or rather stored in a a separate index table after extraction.

    I can’t answer questions about the Pro version here, for that please contact us. (Not that I don’t want to, but it is against the forum rules to discuss it, it will get us both in trouble).

    All the best,
    Ernest

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.