DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Display Module on all pages

 3 Replies
 1 Subscribed to this topic
 12 Subscribed to this forum
Sort:
Author
Messages
Growing Member
Posts: 78
Growing Member

    Hello,

    I think I might have a problem as soon as my web site launches.  I have a html module which I added to header portion of skin, and chose option to display on all pages.  This module contains html and will be seen by crawlers.  What I do not want is crawlers to index the content on any other page other than home page.  You see, it has company name, phone number, etc within the content. I have over several hundred pages with module in header on those pages. What are my options here?  Any suggestions are appreciated, and thank you in advance.  

    My though was a sql script to change index property on all modules excepy home page , but sounds a bit tricky to me. 

    Senior Member
    Posts: 1404
    Senior Member

      Hello John: 

      FYI - I've moved your post to another forum that might be more appropriate.  :)  

      There are a lot of ways to potentially accomplish what you're trying to do.  However, the way search engines work, they actually intend to see and consider the content on the page that all users will see.  If a search engine like Google detects that the page is loading differently to the indexing bot versus what is sent to end users, the SEO of that website will be dinged. 

      It seems that you know that content seen on every page is deemed important by a search engine, for the very reason we might think...  If the content is on every page, it's because you deemed it to be important to the user experience of your visitors. However, if this is the case, then users might be searching for it.  So, you might be hoping that you can direct people to the correct page, instead of another higher-value page that might only have that content in the footer.  (This is technically handled in most cases through modifying the content and metadata of the pages in question, by testing, modifying, indexing, then testing again.)  

      With that being said, it would be possible for you to dynamically hide a pane in your theme, based on the user-agent.  You'd just add some additional server-side code to show/hide it based on the page URL.  

      You can use tags in the module settings for a module.  When this is used, you'll again add some server-side code to the theme in this scenario.  This code would traverse the module properties of the modules as they are loaded, and then modify the module's properties to show/hide it, based on the tags and the page URL in question.  

      If this is a chunk of HTML content that's being loaded by a structured content solution, then you can potentially do the same thing outlined above, but this time you'd do it within the structured content template, instead of the theme.  In this scenario, you might even be able to handle the conditions in a more configurable way, versus a completely code-first solution.  

      Growing Member
      Posts: 78
      Growing Member

        Thanks Will,

        I just do not want the same html to be shown on google or any other search engine for every page - wouldnt that be bad idea?

        Senior Member
        Posts: 1404
        Senior Member

          It's a valid concern, but as long as each page has a purpose that also includes content that supports that purpose, I have rarely seen this happen.  Developers tend to worry about it happening far more often than it actually does.  Google is pretty smart (usually).  ;)  

          These Forums are dedicated to the discussion of DNN Platform.

          For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

          1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
          2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
          3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
          4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
          5. No Flaming or Trolling.
          6. No Profanity, Racism, or Prejudice.
          7. Site Moderators have the final word on approving / removing a thread or post or comment.
          8. English language posting only, please.

          Would you like to help us?

          Awesome! Simply post in the forums using the link below and we'll get you started.

          Get Involved