Great minds think alike

Our Knowledge Base is partially publicly available and indexed by Google. It features a lot of content both for existing customers but also potential customers (e.g. they wanna know in detail how to use the product before buying, or are googling for a specific issue that our product can solve). Therefore the Knowledge Base has SEO potential to increase traffic and leads.   However right now it is impossible to do advanced SEO optimisations for KB articles, as basic SEO meta-data fields are not available to edit specifically.   Please add (at least) the possibility to edit these for each page: Page Title Meta-Description   Furthermore these functions could be also useful in regards to SEO: Possibility to redirect a KB page to another URL Possibility to set the robot meta-tag at a page level: index / noindex   Thanks, ...read more

According to HubSpot's Support team, whether a HubDB created Page appears in the XML Sitemap or not can only be controlled at subfolder level.    We have a scenario where a parent page should be indexed by search engines, but the many pages within the subfolder should not. Unfortunately, this means the entire subfolder of content has to be included in the sitemap so that the parent page is easily indexed.    We've added a noidex code to the subpages, but at scale this is a huge number of pages we're telling search engines to crawl via the XML sitemap, only to then say "don't index".   And the result is that we have thousands of these noindex pages clogging up Google's crawls of the site, and significantly delaying the indexation of new content.    A solution like a Yes/No column in the HubDB table that says "Include XML Sitemap" would be ideal. We've tried developing one, but it is not being recognised by HubSpot and is being overridden by the Subfolder rule mentioned above. ...read more

Description: Implement a feature allowing for the customization of meta and title tags on author pages to accommodate varying lengths and strategic content, instead of being restricted to a fixed format.   Possible Actions: Enable variable length settings for meta descriptions to ensure they can be concise when necessary or detailed for complexity, adjusting dynamically to the content's needs. Allow title tags to include essential keywords or phrases that reflect the current focus areas or expertise of the authors, regardless of their length. Why: The current limitation is that meta descriptions and title tags on author pages are static and confined to a one-size-fits-all model, which isn't always effective. This restricts our ability to:   Optimize for Search Engines: A fixed-length meta description may not always use the optimal number of characters necessary to rank well in search engines or to entice clicks from potential readers. Reduce Inefficiency: Without the ability to dynamically customize meta and title tags, much manual intervention is required to keep these elements relevant, leading to inefficiencies and missed opportunities.   Customizing meta and title tags dynamically on author pages can help overcome the limitations of traditional SEO and make it more flexible and targeted. This approach will ensure that the metadata is concise and effective, which will improve the visibility and appeal of author pages in search engine results. ...read more

We are working through an issue with one client who hosts their website on Hubspot CMS. Bing stopped indexing their pages in August 2022. Prior to that date indexing was fine.    Researching this Bing (and Microsoft) is suggesting we install IndexNow (https://www.indexnow.org) on the website. CloudFlare has native support for IndexNow but we do not have access to HubsSpots version that is used on our websites hosted by Hubspot.    Upon researching futher, to manually set it up, we need to place an api key in the root domain. Since we cannot do that on Hubspot we are using the workaround by uploading the file and using a Hubspot Redirect.    So far so good. The next problem comes when updating search engines like bing, you need to run a script that submits the pages that changed to the search engine. Cannot do that with Hubspot, even though Hubspot knows when page content changes.    The idea is for Hubspot to either support configuring CloudFlare to update search engines automatically when website pages change or to natively support Index Now and send notice to search engines once a day regarding URLs that have changed.    Wordpress has two options, The Yost plugin supports Index Now and Microsoft offers a free plugin to Wordpress that does the same.    Please support Index Now.    Here is the Bing page on the topic. https://blogs.bing.com/webmaster/august-2022/IndexNow-adoption-gains-momentum   ...read more

Currently, when connecting the Google Search Console (GSC) integration with SEO tools inside of HubSpot, it doesn't give you the option to select which GSC properties you'd like to integrate with HubSpot. While SEO Tools will only pull in search data for domains connected to a given portal, meaning that there's no risk of data bleed across clientele domains, it may be concerning for some users– especially those working with agencies– to know that several of their clients' GSC data is technically connected to another client's portal.    Having the option to select the specific domains/ GSC properties you'd like to connect while setting up the integration would be incredibly beneficial and would alleviate this concern.  ...read more

My idea is to grant users the ability to set-up "structured data" on blog posts to help with SEO.   Structured data is a system of pairing a name with a value that helps search engines categorize and index your content. Microdata is one form of structured data that works with HTML5. Schema.org is a project that provides a particular set of agreed-upon definitions for microdata tags.   Structured data seems to matter more often now with search engines and help boost SEO.  ...read more

Hello everyone,   I would like to propose a new feature that I believe could significantly improve the performance and security of our activities on HubSpot: support for HTTP/3.   Reasons for Implementing HTTP/3:   Improved Performance: HTTP/3 is designed to reduce network latency and improve page load speeds. This is particularly useful for those of us using HubSpot to manage websites, landing pages, and dynamic content that require fast response times. Reliability: By using the QUIC protocol, HTTP/3 offers greater resilience to packet loss and connection issues. This means fewer interruptions and a smoother browsing experience for end users. Enhanced Security: HTTP/3 includes end-to-end encryption as a standard, ensuring greater security for transmitted data. This is crucial for protecting the sensitive information we handle on HubSpot. The Future of the Web: As HTTP/3 is the future standard of the web, having HubSpot compatible with this technology would allow us to stay at the forefront and prepared for future developments. Cloudflare and HTTP/3: It's important to note that HubSpot uses Cloudflare, which has already implemented support for HTTP/3. This means the technology is already available and ready to be leveraged. Integrating HTTP/3 into HubSpot could be a natural and relatively straightforward step, given the existing compatibility with the network provider. Positive Impact on HubSpot: Implementing HTTP/3 would not only improve the experience for existing users but could also attract new customers looking for a cutting-edge, high-performance marketing platform. Additionally, with the web increasingly focused on speed and security, adopting HTTP/3 could become a significant competitive advantage for HubSpot. Thank you, Simone  ...read more

There has been a lot of chatter regarding using reporting services like SEMRush and Moz which will give you site audits. Usually, these reports give back information such as errors and issues One of the major errors I've seen reported on a lot of HubSpot sites are the Duplication errors for things such as:   Duplicate content: This is usually caused by the /page/1 not being properly redirected from the start. You have to create three directs total to fix that. Another cause for duplicate content is that listing pages do not have the ability to have a self-referencing canonical (which is fixed with some quick HubL in the blog template header). Duplicate Titles: Caused by all the paginated pages showing the same title. Duplicate Meta Descriptions: Same cause as above The first bullet, as mentioned, can be fixed with using URL mapping tool and HubL, the last two, however, we have zero control over. I know we can use JS to change the titles and meta's for the listing and Google's searching should be ok with checking those differences on the page. This can be tedious to do and a much better way would be to allow us to have a "Page Title Builder" in the SEO & Crawlers Tab. This can let us fi page titles and have them render server side rather than relying on JS to fix things and hoping they will be picked up during the next Google crawl.      I have created a mockup below for this (based on Yoast's SEO WP Plugin) to better explain a possible solution:     Also, I think it would be awesome to have Description fields added to the blog topic's so we can create custom Meta Descriptions based on those topics and not have to rely on just the default blog meta description or one that Google pulls automatically (which is usually the post excerpt of the most recent post for that page).  ...read more

We'd like the ability to save the SEO analytics report that pulls from Google Search Console, and add it to a dashboard. Would be really helpful to add this to our other comprehensive dashboard views.    ...read more