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

Add Orphan Link counter, Add More detailed schemas under Schema, Add some clarity on how to improve content #31

Open
Solutiontales opened this issue Oct 10, 2020 · 1 comment

Comments

@Solutiontales
Copy link

  1. I don’t need to give details about this as you’ll know why Orphan Links hurt seo, and this is one feature which should be added soon.

  2. The schema extension is a paid one, but it has only a basic article schema it should have all different kind of schema.

  3. Many time it says subject not found there should be some pointers on how to improve it.

@sybrew
Copy link
Owner

sybrew commented Oct 13, 2020

Thank you for the feature suggestions! I'm afraid I have to turn them down, here's why:

  1. For this, we'll have to set up a database that counts all your links, even from widgets and menus. This is a drag (easily gigabytes of extra data stored on your servers...), and can better be done from an external server for accuracy and reduced resource spending. Google Search Console already counts the links for you, and they show excluded URLs when there's no "intent" of indexing them, either. The "intent" means that there are no links to the resources. Since these tools exist, I vehemently believe it's best left to them — the hearth in where your content lives.

  2. We can only add more structured data when we can supply the content to support those. For example, since we do not provide "products," it'd be noncoherent for us to supply the "Product" structured data markup. This job is better left for a plugin that provides products, such as WooCommerce — they also aptly supply the necessary structured data. We have no intention of adding these complexities to the plugins because those primarily force vendor lock-in. Moreover, we have yet to spot the benefits.

  3. Please see the Focus's FAQ first entry. This FAQ entry is new, and we're planning to add an intricacy to point users to it when we're detecting this common mistake. If you're still finding issues after adjusting (or found that the issue is unrelated), please contact us privately, so we can look at the keywords you're using.

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

No branches or pull requests

2 participants