SibLinks reads a page and suggests where it should link to other pages of the same site: the exact sentence, the words to link, and the page to link to, with a short reason. You add the link with one click in the block editor, the classic editor or Elementor, or mark it on the published page with any page builder.<\/p>\n\n
The plugin interface is in English and can be translated on translate.wordpress.org. Link suggestions are built for Hebrew content: on sites in other languages they are fewer and less precise.<\/p>\n\n
What you get<\/strong><\/p>\n\n Requires a SibLinks account<\/strong><\/p>\n\n Link suggestions are computed by the SibLinks service (see \"External services\" below). You need a SibLinks account, a Site ID and a Secret from the customer area at https:\/\/app.siblinks.co.il. Each check of a page uses one check from your account balance. New accounts get free trial checks. Link health and the Search Console data work without an account.<\/p>\n\n This plugin connects to the SibLinks service (https:\/\/api.siblinks.co.il), which computes the link suggestions. It is operated by SibLinks (https:\/\/www.siblinks.co.il). Nothing is sent before the site owner enters a Site ID and a Secret in SibLinks > Settings.<\/p>\n\n What is sent, and when:<\/p>\n\n The service processes the content to compute suggestions and does not store it. The service may use third-party processing providers, as described in its privacy policy.<\/p>\n\n The plugin does not connect to Google. The Search Console file you upload is read on your site and not kept; only the numbers per page (clicks, impressions, CTR, average position) are kept in your site's database, and they are never sent to the SibLinks service or anywhere else.<\/p>\n\n Link health requests only your own site's pages (to see which links are broken or redirect), from your server, and sends nothing to the SibLinks service. The strength of the pages, the link counts and the files you download are worked out on your site and are not sent anywhere.<\/p>\n\n Page summaries are built on your site and kept in its own post meta ( Optional: the connection values can be set in wp-config.php instead of the database:\n define( 'SIBLINKS_API_BASE', 'https:\/\/api.siblinks.co.il' ); define( 'SIBLINKS_SITE_ID', '...' ); define( 'SIBLINKS_SECRET', '...' );<\/p>\n\n\n No. Every link is added only when you click \"Add link\", and you can undo it before saving.<\/p><\/dd>\n No. Only \"Add link\" and, in Link health, \"Fix\" change a page, and only when you click them. \"Fix\" replaces the address of a link that goes through a redirect with the right address. Before the change WordPress saves the current version in the page's revisions, so you can restore it.<\/p><\/dd>\n Only the page you chose to check, rendered as a logged-out visitor would see it. Published pages, drafts, pending and scheduled pages can be checked. Private and password-protected pages are not sent unless the site owner enables it in the settings. Nothing is sent until a user starts a check. See \"External services\".<\/p><\/dd>\n By default authors and above, on the pages they may edit. The setting \"Who can run a check\" changes it, and developers can use the filter Yes. In the block editor, the classic editor and Elementor (Text Editor widget) the link is added in place. With other builders the suggestion is marked on the published page and the link is copied, so you can paste it in the builder.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
External services<\/h3>\n\n
\n
\n
Privacy<\/h3>\n\n
_siblinks_profile_v1<\/code>). Link check results are kept in post meta (_siblinks_link_check_v1<\/code>). The strength of the pages is kept in the option siblinks_strength<\/code>. Uninstalling the plugin removes its tables, options and post meta.<\/p>\n\nSecurity<\/h3>\n\n
\n
\n
siblinks<\/code> folder to \/wp-content\/plugins\/<\/code>, and activate it.<\/li>\n\n
Does the plugin add links by itself?<\/h3><\/dt>\n
Does the plugin change my pages by itself?<\/h3><\/dt>\n
Which content is sent?<\/h3><\/dt>\n
Who can run a check?<\/h3><\/dt>\n
siblinks_user_can_run_check<\/code>. Checking many pages at once needs at least author permissions, and searching for \"pages that could link here\" needs editor permissions.<\/p><\/dd>\nDoes it work with page builders?<\/h3><\/dt>\n
0.19.0<\/h4>\n\n
\n
0.18.2<\/h4>\n\n
\n
0.18.1<\/h4>\n\n
\n
0.18.0<\/h4>\n\n
\n
0.17.1<\/h4>\n\n
\n
0.17.0<\/h4>\n\n
\n
0.16.1<\/h4>\n\n
\n
0.16.0<\/h4>\n\n
\n
siblinks<\/code>), and new names for its settings, tables, hooks and constants (siblinks_<\/code>, SIBLINKS_<\/code>). It does not read the data of the old plugin: remove the old one, install this one and enter the Site ID and Secret again.<\/li>\n0.15.0<\/h4>\n\n
\n
0.14.0<\/h4>\n\n
\n
0.13.0<\/h4>\n\n
\n
0.12.0<\/h4>\n\n
\n
0.11.0<\/h4>\n\n
\n