• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Feast Design Co.

WordPress Themes for Food & Lifestyle Bloggers

  • Themes
  • Feast Plugin
  • Blog
  • Support
  • Tutorials
  • Nav Social Menu

    • Email
    • Facebook
    • Instagram
    • Twitter
menu icon
go to homepage
  • Feast Plugin
  • Support
  • Tutorials
  • Account
    • Facebook
    • Instagram
    • Twitter
  • search icon
    Homepage link
    • Feast Plugin
    • Support
    • Tutorials
    • Account
    • Facebook
    • Instagram
    • Twitter
  • ×

    Home » Food Blog Design and Appearance

    Advanced "Jump To" Links

    Published: Jan 7, 2020 · Modified: Feb 22, 2023 by Skylar · 27 Comments

    This tutorial features the Feast Plugin, which enhances and extends your theme to improve SEO, pagespeed, accessibility and user experience.

    The purpose of the Feast Plugin's Advanced Jump To Links is to:

    • provide your readers with a better on-page navigation experience
    • generate additional links in the search results for your heading tags

    The core of it breaks down into two features that when combined, can qualify you for additional links in search engines, and hugely improve your on-site user experience:

    1. Page anchors, also known as anchor tags, jump links, or "Page Jumps" in WordPress
    2. An expanded "jump to" menu that links to your h2 tags

    We should say up front that there's no guarantee that all (or any) of your recipes will get these links. Search engines reward high quality content with additional rich search results, and if you're not generating these links then there may be a quality issue with your page content or site structure.

    Additionally, these jump to links are typically only found in the top 5 positions in the search results. If you're in position 6 and lower, it's unlikely to show.

    These particular rich snippets are driven exclusively by on page formatting and not structured data, and can be shown as a "Jump to (heading)" or as additional links below your regular page description:

    For clarification, your header is the top section of your website, a heading is an h2 element in your content.

    This feature deals with headings and is not related to headers.

    And in case you were wondering how they look on site, here is the feast_advanced_jump_to block live:

    Jump to:
    • How to use it
    • Why is it blurred in the block editor?
    • Guidelines
    • Why use it?
    • Automated page jumps
    • Automatically insert into posts
    • Why only h2s?
    • Expanded "jump to" menu
    • Search engine benefit
    • Examples
    • Rewrite your heading tags
    • How does a link to an anchor (page jump) affect SEO?
    • Using the block editor
    • Do emojis work?
    • Replace the recipe card heading
    • Link to the comments
    • Default closed
    • Max height box + scroll
    • Non-english characters
    • Google Search Console
    • Future development

    How to use it


    Note: we no longer recommend making this a reusable block due to WordPress breaking it frequently.

    Update to the Feast Plugin 3.5.0 and simply insert the feast_advanced_jump_to shortcode where you want it to display.

    As of version 4.4.0, do not use the shortcode, use the "Advanced Jump to" block:

    placeholder image for the advanced jump to block
    note that the h2s will not populate in the block editor

    To access it, click the (+) button in the block editor and search for "advanced":

    inserting the advanced jump to block, in the block editor

    We do not recommend displaying this above-the-fold. Your posts should start with an introductory paragraph for the reader, followed by an image of the finished recipe (also below the fold), and then the jump links.

    Why is it blurred in the block editor?

    Adding functionality to the block editor to read, display, and update the headings in real time would add a ton of javascript that would bloat the already-bloated block editor even further.

    If you follow the guidelines (below), then it's unnecessary to have to review it while editing, and you can simply view it live.

    You can also click the circular ℹ️ button in the block editor to view the live document outline:

    Guidelines

    We've created a modern guidelines for page headings.

    It's critically important that you re-learn how to write headings, because almost nobody in food blogging does this correctly. Headings are a topic that simply have not received any attention before we wrote the modern guidelines for page headings.

    These guidelines are for accessibility and SEO compliance:

    • do not use headings for styling text
    • do not use headings for full sentences
    • write your headings as "section" headings
    • write headings for screen readers, and avoid acronyms
    • do not use your keywords in your headings
      • ignore Yoast's recommendations - they're outdated
    • do not use too many headings - aim for 5 to 10
    • use headings sequentially
      • personal recommendation: recipe posts don't benefit from using anything aside from h2

    See the modern guideline for page headings document for additional details.

    Why use it?

    Feast declared 2019 the year of user-experience (I know - we missed releasing it in 2019). We wanted to make food blogs better for the reader, and one of the most popular recent UX (user-experience) changes was the presence of "jump to recipe" buttons.

    While it's a great feature, it doesn't come close to the full potential.

    All heading tags on a page, not just recipes, can contribute to a better user experience. Google even has an entire section on headings in their SEO document.

    Automated page jumps

    The WordPress document on page jumps explains the why and how to do it. It also goes more broadly by the name "anchor links".

    These are unquestionably a huge UX benefit to readers, but are traditionally tons of extra work.

    Extra work that we know you don't have time for. Not only would you have to add an id tag to every heading on the page, but you also have to then link to those headings.

    That's why doing this in an automated way makes sense.

    Technical note: we make use of the WordPress core sanitize_title() function, which is how your post title slugs are built by WordPress. We also perform a little pre-cleaning of the title, removing all characters that aren't letters (a-z), numbers (0-9), or spaces.

    This is only applied to h2s.

    Automatically insert into posts

    We intentionally don't allow this to be automatically inserted into every post, like some other plugins do.

    This is because no site we've ever seen has properly used h2s from the start. This means that some posts on every site:

    • use a paragraph in a heading
    • overstuff the keywords into headings
    • incorrectly use h2s where h3s should be used
    • don't follow Google's guidelines on headings
    • don't follow accessibility guidelines on headings

    While automatically inserting the Jump To would be more convenient for most posts it would cause major issues on other posts. The posts that have major issues could contribute in an unhelpful content penalty that then negatively affects the entire site, including the top ranking posts.

    Ultimately, using the Advanced Jump To needs to be done as part of a broader recipe post update, which includes fixing and correctly using headings to comply with Google and accessibility guidelines.

    Why only h2s?

    The decision to exempt everything except h2s was done to keep the page navigation menu focused and comply with both Google's Webmaster Guidelines and screen reader preferences.

    Use heading tags where it makes sense. Too many heading tags on a page can make it hard for users to scan the content and determine where one topic ends and another begins.

    Google Webmaster Guidelines for Heading Tags

    Do not overuse headings. In most cases, content editors will not need more than <h2> rank headings and the occasional <h3> rank.

    Yale web accessibility guidelines on headings

    The fact is that 99% of recipes simply don't need anything more fine-grained than h2s.

    You can still use h3s and below if you think you need to, they just won't show up in the jump to menu.

    Expanded "jump to" menu

    If you've ever taken a hard look at the keywords that your recipes get in Google Search Console, you'll see that visitors don't come to your post looking for just one thing.

    There's hundreds of different queries about a recipe you've posted, that your readers could have questions about.

    In keyword research, this is known as the "long tail", and it's loooooong. The primary keyword on well ranking posts sometimes drives less than 30% of the traffic.

    Your actual recipe is the star of the show, which is why the "jump to recipe" button has thrived.

    But they also want to know about:

    • ingredients
    • instructions
    • cooking time
    • calories
    • substitutions (turkey, chicken, beef, pork, lamb)
    • scaling the recipe up, or down
    • variations (how to make: keto, paleo, gluten free, whole 30)
    • how to store it
    • how to freeze it
    • how to reheat it
    • related recipes

    This isn't just a great user experience, providing a one-stop-shop for all things about that recipe, it's also beneficial for search engines.

    Adding headings addressing these questions and long tail keywords means that your article can show for more queries, getting you more clicks and pageviews.

    See this post on click through rates.

    Note: do not overoptimize your headings, exclude the primary keyword per the modern guidelines for page headings.

    Search engine benefit

    "Jump to" links are still (and may always be) a result of in-content post structure.

    Example of "jump to" link in the search results, going to a heading on the page

    From an SEO perspective, keyword usage in the page title is still a good practice, but do not do this for heading tags within the post. The heading here is actually incorrectly done, and shouldn't be using the primary keyword.

    Your heading tags are headings for your readers. Anything you read about heading tags having to exact match keywords is long outdated - stuffing keywords into heading tags will not make you rank higher.

    What this will do if properly implemented (see: word of caution below), is make it possible to generate additional links on your search engine listing.

    This means that instead of a single link that may not match a user's query, they're presented with anywhere from 1-3 additional text links that may catch their attention or draw them in.

    Example of extra links in search engines
    WordPress' own Page Jumps page, contains these links thanks to the id anchor

    Not only does this make it seem like your post is more thorough, using good headings means you can pull people in with questions they may not even know they had.

    This generates additional clicks for the same post, leading to more pageviews.

    Examples

    What does this look like in the real world?

    Recipe with jump links from wikihow.com

    I have no idea what hardtack is, but I do want to know how to make it soft vs. hard, or fried. Note: the above is actually poor use of heading tags, as the primary keyword is repeated in the heading (don't do this!)

    savory instant pot barley with jump to links
    beyondmeresustenance.com

    Another example with some emojis, and a useful direct link to ingredients.

    Jump links also work on non-recipe posts, like this one from espressocoffeeguide.com

    I have a 10 cup coffee maker, and no idea how many scoops or tablespoons (or pinches?) of coffee it should have. I probably wouldn't have searched for "conversions" but that could be useful.

    You can also generate headings with emojis, which are more eye catching and could lead to higher click-through-rates (see further below):

    Rewrite your heading tags

    This feature requires that you've been responsible with your usage of heading tags. In most cases, you'll want to rewrite the heading tags using our modern guidelines for page headings.

    Casey Markee has pointed out that some questionable SEOs have recommended putting entire sentences and paragraphs into h2 tags.

    This is absolutely not a valid thing to do.

    Headings should only be used to break your content into more easily-consumable chunks, centered around the sub-topic introduced by the heading.

    Sources:

    • Yoast: Basics of heading tags
    • Use heading tags for hierarchy, not styling

    There are also conventions to follow when using headings, such as only capitalizing the first letter:

    Google's Heading Capitalization Guidelines

    From: https://developers.google.com/style/capitalization

    How does a link to an anchor (page jump) affect SEO?

    Should you be concerned if people begin linking to a specific part of your page? eg. https://yoursite.com/your-best-recipe#how-to-make-it-paleo

    No.

    Google calls these parts of the links "fragments", and for the purposes of link equity they just count towards your main post URL.

    A fragment (in this case, "#info") generally identifies which part of the page the browser scrolls to. Because the content itself is usually the same regardless of the fragment, search engines commonly ignore any fragment used.

    Google Webmaster Guidelines on link fragments

    Google also considers linking to headings as perfectly legitimate, and provides guidelines for how to use it: https://developers.google.com/style/headings-targets

    Note: these are not the same thing as site links. You can not control site links.

    Using the block editor

    The Feast Plugin adds an "Advanced Jump to" block that makes inserting this into each post, easy:

    For performance reasons, the block renders with placeholder content in the editor:

    Then populates only on the front end.

    Do emojis work?

    Everything that isn't a letter or number if stripped, so emojis are fine.

    As a best practice, we wouldn't recommend using these for headings in recipes.

    Use emojis in headings to boost your click through rates!

    edit: release 3.5.2 allows for emojis in the anchor text, but still strips it from the anchor link.

    Replace the recipe card heading

    By default, recipe cards output the recipe title as a heading, and this creates a keyword-stuffed heading that goes against best practices.

    It also doesn't tell the reader it's the recipe card - it's just the post title, repeated.

    Instead, we recommend using the setting in the plugin to insert the word "Recipe" or "Recipe Card" in the Feast Plugin settings page:

    setting to replace the recipe card heading

    This is a more technically correct implementation that follows the "use short, concise headings" rule.

    Link to the comments

    In the Feast Plugin settings page, you can enable a link to the comments directly from the Advanced Jump To block:

    Default closed

    There's an option in the Feast Plugin to "Default Closed" site-wide if you'd prefer the menu to load compressed. This will still generate jump to links in the search results.

    Clicking on the block will then expand the menu.

    We do not recommend using this setting as it will cause CLS issues. Instead, use the "max height" feature below.

    Note: Defaulting closed on a single post is not possible.

    Max height box + scroll

    This option locks the Advanced Jump To at a specified height, and uses a scroll bar for any items that extend beyond that height. This prevents the table from becoming too large on longer posts, which can improve mobile usability.

    Accepted range is 100 to 500. Recommended: 300. Set empty to disable.

    Note: for recipes, you should still keep the number of headings short and concise to comply with both search engine + accessibility best practices.

    Non-english characters

    By default, we strip out any characters that may cause unexpected behavior (anything that isn't A-Z or 0-9). In order to display non-english characters, you'll need to modify the behavior using a code snippet:

    add_filter(
    	'feast_clean_title',
    	function( $_, $original ) {
    		return $original;
    	},
    	10,
    	2
    );

    We recommend testing this on a staging site before doing it on a live site.

    Note: this will keep any existing emojis from the heading in the anchor text, which is untested and has unknown consequences. If you enable this setting, we recommend not using emojis in headings.

    Google Search Console

    As Google indexes the jump-to links, they'll begin showing them in the search results and recording those links impressions+clicks, which can skew results.

    You can filter these out of a report by choosing to exclude URLs containing a hashtag/pound (#):

    Future development

    We'll continue developing this based on feedback you provide. Among the things we need to know you're interested in are:

    • How this works on non-english blogs (eg. accented characters?)
      • Yes, as of 3.5.2 you can use any UTF-8 character, which should include non-english languages
    • Screen readers - whether the "jump to" links should be tabIndex'd, have alt/title descriptions, or hidden
    • We've made the decision to only focus on h2 at the moment, in order to keep the "jump to" menu at a reasonable size per SEO and accessibility
    • Making the table of contents sticky as users scroll, and/or integrating it directly into the header/menu bar
    • Should we automatically add jump to links for "Comments"?
      • Setting added to 3.6.0 to enable link to comments if 1 or more comments exist
    • Should we replace the recipe card titles with a more generic "Recipe" link?
      • Setting added to 3.6.2 to enable custom heading in place of recipe card title
      • The heading "recipe" is better than repeating the post title, which can be confusing

    Isn't this just a table of contents?

    Yes.

    And no.

    While some other table of contents plugins are similar, we've designed this with built-in best practices based on Google and accessibility guidelines. This is a next-level approach that:

    • creates fewer website errors: it doesn't use javascript so that page loading times aren't affected
      • some other table of contents plugins build the table using javascript, slowing render times
      • some other table of contents plugins use javascript to initiate an unnecessary "smooth scroll" effect that negatively impacts user experience
      • additionally, some users have javascript disabled
    • optimizes for SEO: it uses keyword-optimized anchor text
      • some other table of contents plugins use non-user-friendly anchor text such as #heading-1, #heading-2, etc.
    • optimizes for accessibility: it has best practices built in
      • too many options aren't always good: too many headings are bad for screen readers and go against search engine guidelines for headings - h3s and lower generally aren't necessary for recipe sites
    • provides a better user experience: it uses the fully-supported <details> html element to allow users to minimize the table of contents without javascript

    Aside from some technical differences, we don't think of this as simply a table of contents. You should think of this as a way to expand on something visitors already love: jump to buttons.

    We mentioned above that the long-tail for successful recipe posts is huge, sometimes accounting for over 50% of the traffic. Following modern guidelines for page headings directly helps that long-trail traffic, providing a better user experience as well as enhancing your search engine listing with rich snippets.

    Additional notes

    • In version 5.5.4, you can now use non-English characters
    • As of 3.6.2, we remove all existing IDs on h2 tags
    • You can replace the "Jump To" text with a new setting in 3.6.0
    • You can replace the recipe card link with custom text in 3.6.2
    • You can filter the output using the feast_filter_advanced_jump_to filter as of 3.6.0
    • Potential issue: we're not yet sanitizing duplicate IDs, and while the affected users for this would be extremely small (you've added your own custom IDs on non-h2 elements) and non-breaking (violates nerdy technical guidelines, but no display issues), it should be fixed in a future version
    • In version 6.5.6 we removed h2 margin/padding originally used to ensure the heading was being displayed - this caused too many other problems

    More

    • Horizontal scrolling
    • Subscribe button
    • Favicon
    • FSRI Block

    Reader Interactions

    Comments

    1. Tamar says

      January 11, 2020 at 11:37 pm

      I just implemented this and have two points for feedback -

      1 - I use WP Recipe Maker for my recipe plugin. The shortcode picks up the the recipe title (I guess it's an H2). In order to not make the link sound redundant, I have to put the word "recipe" in the recipe title (ie H2). This is unnatural. It also makes the Jump To Recipe redundant, but I think the styling/placement of the recipe jump link at the top is effective, so I don't really want to remove it.

      2- "We also perform a little pre-cleaning of the title, removing all characters that aren't letters (a-z), numbers (0-9), or spaces." This is pretty close to a deal breaker for me, because of #1 above. I am a kosher food blogger and put a designation in parentheses in every single recipe title indicating whether the recipe is meat, dairy, or neither. This renders as "New York pizza dairy" in the automatically generated jump link, which again, is really unnatural.

      In sum: if I change my recipe title from "New York pizza (dairy)" to "New York pizza recipe" my jump link makes sense, but the recipe card looks odd, and I lose vital information.

      Thanks for taking this into consideration.

      Reply
      • Skylar Bowker says

        January 13, 2020 at 5:47 pm

        Thanks so much for the feedback Tamar!

        1. We could in theory automatically insert an <h2>Recipe</h2> right in front of the recipe card, and skip the recipe card's title. This would also work with Create. Would this be useful?

        2. Thanks - 3.5.2 was just released, which leaves formatting in place for the anchor text. This should make it usable for you. The link/heading-id itself is still filtered however, to remain compliant with URL standards.

        Skylar

        Reply
        • Mary Ann Kelley says

          January 20, 2020 at 1:52 pm

          It would be great if there was a way for us to choose whether to include h2 in the recipe card title or not. I think (not 100% sure) I would prefer to manually add an h2 tag with my choice of emoji above the recipe card and have that picked up instead (or if you decide to automatically insert an h2 for Recipe, if we could choose our emoji for that specific h2 in Feast settings).

          Right now I've got my first recipe set up with the emoji but the recipe card h2 sticks out in the jumplinks since it has no emoji and is in different capitalization than the other h2 titles (they are using lowercase as suggested, but my recipes have all words capitalized).

          Reply
          • Skylar Bowker says

            January 20, 2020 at 2:10 pm

            Coming out today 🙂

            Just wrapping up some testing.

            Reply
            • Mary Ann Kelley says

              January 20, 2020 at 2:39 pm

              Wonderful! Thanks.

              Reply
    2. Mary Ann Kelley says

      January 12, 2020 at 9:08 am

      I'm inserting [feast_advanced_jump_to] in the classic editor text area and am not getting the links (there are h2 tags on the page). Is this something that is only available in blocks?

      Reply
      • Skylar Bowker says

        January 12, 2020 at 3:21 pm

        Hey Mary Ann,

        Without knowing more, I couldn't provide any sort of guidance. It does display on the front end when used in the classic editor.

        Please submit a support ticket: https://feastdesignco.com/support/

        Reply
    3. Lucy Allen says

      January 22, 2020 at 4:12 pm

      Sorry if this should be a support ticket instead. I added jump to links yesterday and noticed the updated version today which fixed the duplicate recipe link I had seen yesterday, thanks for that. Yesterday the jump to links worked but today I’ve noticed that not all of the links are working in my posts. Several do but some in the list are not. I just wondered if anyone else has reported the same.

      Reply
      • Skylar Bowker says

        January 23, 2020 at 4:46 am

        We tracked down the cause of this issue, and it was due to the h2 heading being combined with the <strong> tag. The headings guidelines have been updated with this information: https://feastdesignco.com/modern-guidelines-for-page-headings/#do-not-combine-with-other-tags

        Reply
    4. Mirna says

      June 10, 2020 at 12:26 pm

      Love when you add video tutorials! Thank you!! It helps sooo much!!

      Reply
    5. Caitlin says

      September 16, 2020 at 12:40 pm

      I replaced the recipe card header which looks great in the drop-down menu, but it is showing up as a left-aligned header above my recipe plugin. Is there a way to make this center aligned to be consistent with the rest of my format?

      Reply
      • Skylar says

        November 23, 2020 at 9:52 am

        The inserted heading should inherit the same styling as the rest of the headings - send in a support ticket if this isn't the case.

        Reply
    6. Mary Ann Kelley says

      November 09, 2020 at 11:14 am

      Does the code limit the use of the [feast_advanced_jump_to] shortcode to only posts and not pages? Without getting into a discussion of site architecture and why I'm using pages in this particular instance, I'd like to know if I can call the shortcode in a template that is used on pages.
      Using:

      in the page template returns the text [feast_advanced_jump_to].
      Am I missing something, or is impossible to use in templates and/or on pages?

      Reply
      • Skylar says

        November 23, 2020 at 9:51 am

        This should work on pages as well as posts, and we've tested it on other sites, eg. https://espressocoffeeguide.com/gourmet-coffee/asian-indonesian-and-pacific-coffees/indonesia-coffee/sumatra-coffee/

        I'd recommend using the block though, not the shortcode.

        Reply
    7. Matt says

      November 20, 2020 at 1:10 am

      Hey,

      I love this feature, just what I'm after. I'm currently using Yoasts TOC block though, which I wish had a toggle to close. I'd like to use this instead, but what future compatibility will there be between both plugins? It seems like letting the SEO plugin handle this TOC feature seems more future proof than depending on Feast plugin in case I decide to not use my theme anymore.

      I could always move away from Yoast as well some time in the future, but being such a prominent plugin I assume whatever new alternative is out there will have ways of importing over TOC blocks. I doubt they'll allow for importing Jump links from Feast though.

      So what to do?

      Reply
      • Skylar says

        November 23, 2020 at 9:49 am

        This is a little tricky.

        I believe we have a superior implementation than Yoast, and they have some questionable practices. For example, they currently insert heading links into ALL content regardless of whether it has a TOC block or not, which can cause invalid HTML via duplicate IDs. We've raised this issue with them and asked them not to modify content that doesn't have their TOC block.

        Additionally, they support all heading levels, whereas we only support h2s. My opinion is that excessive use of heading links actually HURTS accessibility and UX, not improves it. I'm not aware of any use case for h3/h4/h5/6 with recipe content. They're not technical documents.

        With respect to long term maintainability, we're not going anywhere and the Advanced Jump To is a very useful feature that we plan on maintaining. Yoast is also a solid company and their TOC block may be "good" in 6-12 months, and is most likely supported long term. The benefit of the Feast Jump To is that we have more direct control over it, and can integrate it in different ways in the future (we have plans for this next year).

        Reply
    8. Veena Azmanov says

      January 11, 2021 at 3:28 am

      Is there a way to add the 'jump to' for my whole site... all recipes at once? I don't want to go to each and every recipe to add the code! I have almost 1000 recipes!
      I am currently using a Table of content plugin that I can remove by just deleting the plugin. I have not had issues with that plugin but I would very much like to use this instead of that.
      Thank you so much
      Veena

      Reply
      • Skylar says

        January 11, 2021 at 8:32 am

        No.

        99% of blogs have never properly used headings: https://feastdesignco.com/modern-guidelines-for-page-headings/

        Keyword stuffing is an outdated practice that NEGATIVELY impacts your posts and adding jump to links for these makes the issue worse.

        You should update your posts as you normally would:

        1. updating the content to address reader questions
        2. adding alt text to images missing them
        3. internally linking to new posts
        4. fixing mistakes in old content (eg. keyword stuffing)
        5. take the time to intentionally fix your headings
        6. and then introduce the advanced jump to links

        It's a piece of a larger puzzle.

        Reply
    9. kate-0362 says

      April 19, 2021 at 8:59 am

      Hi, my Jump To box is all in italics - including the emojis which are all wonky! Is there a way to customise the font on this? Or is it just me - none of the examples I have seen are in italics. Thanks!

      Reply
      • Skylar says

        June 17, 2021 at 6:09 pm

        This sounds like a customization you've made - please submit a support ticket.

        Reply
    10. Adrianne says

      June 17, 2021 at 3:24 pm

      Thank-you Skylar for always being so detailed and thorough in how to use features of the Genesis themes and Feast Plugin such as this video tutorial. It makes it SO easy to follow and implement as it should be. The level of detailed and clear instructions is appreciated. Cheers

      Reply
    11. Kachina says

      December 14, 2021 at 2:17 am

      Hiya, if we have a particularly long post I think some users might find it useful to jump back to the menu (e.g. in a long roundup). Is it possible to create a "jump to menu" button or link that takes you back to this menu?

      Reply
    12. rmkj says

      January 22, 2022 at 9:40 am

      Hi, how do you change the styling of the "Advanced Jump To"?

      For example, the background color or outline.

      Thanks!

      Reply
      • Skylar says

        January 24, 2022 at 5:15 am

        This would be done with standard CSS and the "inspect element" tool in your browser: https://feastdesignco.com/how-to/use-inspect-element-troubleshoot/

        Reply
    13. Jasline says

      August 12, 2022 at 2:21 am

      Hi! Thank you for the tutorials, they are very helpful and I always learn new things whenever I revisit them. Can I check if it's possible to incorporate a "Back to Top" for Feast Plugin? Sometimes the article can be very long and very tedious to scroll, especially on a mobile. Thank you!

      Reply
    14. Shannon says

      February 02, 2023 at 1:18 pm

      I understand the benefit of using emojis so that the Jump To links stand out and are more distinguishable in SERPs but I would prefer to not use the emojis within the post itself for each H2. Is there a way to include the emojis just in the Jump To List (assuming that is where Google is pulling the emojis from) and not on each H2 within the post?

      Reply
      • Skylar says

        February 03, 2023 at 6:07 am

        What you're describing is possible from a technical standpoint, but would require site-specific development by a private developer.

        Reply

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Primary Sidebar

    Themes

    • Feast Plugin grants access to all 5 themes
    • Not sure where to start? See the getting started guide

    Feast Plugin

    • Feast Plugin
    • Modern Homepage
    • Modern Sidebar
    • Modern Footer
    • Modern Mobile Menu
    • Modern Menu
    • Modern Recipe Index
    • Modern Categories
    • Modern 404
    • Recipe Update Checklist
    • Recipe Post Template

    Resources

    • Image optimization
    • Recipe Guidelines for Foodie Bloggers
    • How to write a recipe post
    • Page headings
    • SEO for Food Bloggers
    • Tutorials
    • Pagespeed Audit
    • Comments
    • Internal links

    more resources →

    Categories

    • Modern Recipe Index
    • Modern Categories
    • Posts per Page
    • How to use categories
    • Category pages need content
    • How to configure the category pages
    • Food blog site structure
    • Food blog page structure

    Classic themes

    The classic themes are only for hobby sites and any food blog interested in monetizing or SEO needs the Feast Plugin.

    • Foodie Pro Classic
    • Brunch Pro Classic
    • Cook'd Pro Classic
    • Cravings Pro Classic
    • Seasoned Pro Classic

    Footer

    ↑ back to top

    Topics

    • Food Blog Design and Appearance
    • Productivity
    • Tech and Plugins
    • Food Blogging and Promotion
    • Minimalist WordPress Themes
    • Simple WordPress Themes
    • Travel blogs
    • Knitting + DIY blogs

    Help

    • Documentation & Tutorials
    • Food Blogging Resources
    • Open A Support Ticket
    • Login
    • Your Account
    • Subscriptions
    • Downloads
    • Discounts and Coupons
    • Compatibility

    Company

    • Subscribe to newsletter
    • Privacy Policy
    • Refund policy
    • Terms & Conditions
    • Principles and Best Practices
    • Affiliates
    • Contact

    Copyright © 2023 · Feast Design Co.

    Results not typical or guaranteed. Our themes and plugins are just a small part of the overall effort involved in running a food blog. Nothing on this website shall constitute legal or financial advice, always consult a local lawyer and accountant. Accessing this website and all transactions herein are under the laws and jurisdiction of Toronto, Ontario, Canada.