Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong Internal link count when adding new content that is displayed with a shortcode #8768

Open
amboutwe opened this issue Jan 26, 2018 · 3 comments

Comments

@amboutwe
Copy link
Member

Please give us a description of what happened.

When you add a new post/page that will be dynamically displayed using a shortcode, the internal links and, thus orphaned content, is not updated until the post/page where the shortcode is opened and updated.

Please describe what you expected to happen and why.

Internal links would be updated immediately.

How can we reproduce this behavior?

  1. Create (or have) a Local SEO page that displays all locations. Look at the current internal links to another page.
  2. Create and publish a new location. See that the internal link count do not update.
  3. Open the post/page that displays all locations. Change nothing. Click update. See the internal link count change to reflect the new location link.
  • Note this is not specific to Yoast SEO: Local but to any plugin that uses a shortcode to dynamically create linked content. For example, a shortcode that outputs a list of content that matches a specific search criteria like the WPCasa [wpsight_listing_teasers] or [wpsight_listings] shortcodes.

Workaround

After creating new content, open the post/page where the shortcode is used and, without changing anything, click update on the post/page.

Technical info

  • WordPress version: 4.9.2
  • Yoast SEO version: 6.2
  • Relevant plugins in case of a bug: Any plugin that dynamically creates content with internal links through a shortcode.
@amboutwe
Copy link
Member Author

Please inform the customer of conversation # 296032 when this conversation has been closed.

@priscillamc
Copy link

Please inform the customer of conversation # 354640 when this conversation has been closed.

@amboutwe
Copy link
Member Author

amboutwe commented Aug 1, 2018

Please inform the customer of conversation # 410286 when this conversation has been closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants