[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fvkuoh9hwFjjqmuCeVyo3AplSbHKpXexUvF6UPfDxCsw":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":22,"download_link":23,"security_score":13,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":35,"analysis":55,"fingerprints":92},"sitelinks-search-box","Sitelinks Search Box","1.5","apasionados","https:\u002F\u002Fprofiles.wordpress.org\u002Fapasionados\u002F","\u003Cblockquote>\n\u003Cp>\u003Cstrong>PLEASE NOTE\u003C\u002Fstrong>: Since November 2024 \u003Ca href=\"developers.google.com\u002Fsearch\u002Fblog\u002F2024\u002F10\u002Fsitelinks-search-box?hl=en\" rel=\"nofollow ugc\">Google doesn’t support the schema for the Sitelinks Search Box anymore\u003C\u002Fa>. After more than ten years Search Advocate John Mueller confirmed that the feature will be retired and the searchbox will not appear in the SERPs anymore.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Since November 2024 there is no need to install this plugin.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Quoting the post from Google Developers: \u003Cem>While you can remove sitelinks search box structured data from your site, there’s no need to do so\u003C\u002Fem>. \u003Cem>Unsupported structured data like this won’t cause issues in Search, and won’t trigger errors in Search Console reports\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>If you are using tis plugin and reading this readme.txt file, \u003Cstrong>you can uninstall it\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>xxx PLUGIN DESCRIPTION (until November 2024) xxx\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin adds the JSON-LD schema.org markup for the “Google Sitelinks Search Box” on the homepage.\u003C\u002Fp>\n\u003Cp>This new feature of the Google Search Engine was presented on the \u003Ca href=\"http:\u002F\u002Fgooglewebmastercentral.blogspot.com.es\u002F2014\u002F09\u002Fimproved-sitelinks-search-box.html\" title=\"Official Google Webmaster Central Blog\" rel=\"nofollow ugc\">Official Google Webmaster Central Blog\u003C\u002Fa> (05 Sep 2014 07:44 AM PDT). There is more info on the \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fwebmasters\u002Frichsnippets\u002Fsitelinkssearch\" title=\"Google Developers Website\" rel=\"nofollow ugc\">Google Developers Website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>With Google sitelinks search box, people can reach your content more quickly from search results. Search users sometimes use navigational queries -typing in the brand name or URL of a known site- only to do a more detailed query once on that site. For example, suppose someone wants to find that video about the guilty dog on YouTube. They type YouTube, or you-tube, or youtube.com into Google Search, follow the link to YouTube, and then actually search for the dog video.\u003C\u002Fp>\n\u003Cp>The sitelinks search box removes that extra step: a query for youtube displays a site search box in the sitelinks section, letting the user immediately search for that guilty dog video without having to click through to the site first.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>If you use \u003Cstrong>WordPress SEO by Yoast version 1.6 or newer\u003C\u002Fstrong>, you don’t need to use this plugin, as this feature has been included in the version 1.6 update. There is more information in the \u003Ca href=\"https:\u002F\u002Fes.wordpress.org\u002Fplugins\u002Fsitelinks-search-box\u002Ffaq\u002F\" rel=\"nofollow ugc\">FAQ section\u003C\u002Fa> of the plugin.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>What can I do with this plugin?\u003C\u002Fh4>\n\u003Cp>This plugin adds the schema.org JSON-JD markup for the “Google Sitelinks Search Box” on the homepage.\u003C\u002Fp>\n\u003Cp>After activating the plugin you only have to “Wait for Google Search algorithms to identify your site as a candidate for the new sitelinks search box”.\u003C\u002Fp>\n\u003Ch4>SITELINK SEARCH BOX in your Language!\u003C\u002Fh4>\n\u003Cp>The plugin was released first in English and Spanish (es_ES). In the “languages” folder we have included the necessary files to translate this plugin. Translation to ar_SA, tr_TR, de_DE, fr_FR and ru_RU was added in further versions.\u003C\u002Fp>\n\u003Cp>If you would like the plugin in your language and you’re good at translating, please use the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002F\" rel=\"nofollow ugc\">native WordPress Translation\u003C\u002Fa> functionality.\u003C\u002Fp>\n\u003Cp>New to Translating a plugin? First read through the \u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fpolyglots\u002Fhandbook\u002Ftools\u002Fglotpress-translate-wordpress-org\u002F\" rel=\"nofollow ugc\">Translator Handbook\u003C\u002Fa>, then select your locale at \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002F\" rel=\"nofollow ugc\">Translating WordPress\u003C\u002Fa> and finally go to the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fblock-ecommerce-assets-via-robots-txt\u002F\" rel=\"nofollow ugc\">translation page for this plugin\u003C\u002Fa> to translate it.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>You can access the description of the plugin in Spanish at: \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fblog\u002Fmarcado-google-sitelinks-search-box-wordpress-plugin-2873\u002F\" rel=\"nofollow ugc\">Sitelinks Search Box en castellano\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>For further information please send us an \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-sitelinksearchbox-contact\" rel=\"nofollow ugc\">email\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Translating WordPress Plugins\u003C\u002Fh3>\n\u003Cp>The steps involved in translating a plugin are:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Run a tool over the code to produce a POT file (Portable Object Template), simply a list of all localizable text. Our plugins allready havae this POT file in the \u002Flanguages\u002F folder.\u003C\u002Fli>\n\u003Cli>Use a plain text editor or a special localization tool to generate a translation for each piece of text. This produces a PO file (Portable Object). The only difference between a POT and PO file is that the PO file contains translations.\u003C\u002Fli>\n\u003Cli>Compile the PO file to produce a MO file (Machine Object), which can then be used in the theme or plugin.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>In order to translate a plugin you will need a special software tool like \u003Ca href=\"http:\u002F\u002Fwww.poedit.net\u002F\" rel=\"nofollow ugc\">poEdit\u003C\u002Fa>, which is a cross-platform graphical tool that is available for Windows, Linux, and Mac OS X.\u003C\u002Fp>\n\u003Cp>The naming of your PO and MO files is very important and must match the desired locale. The naming convention is: \u003Ccode>language_COUNTRY.po\u003C\u002Fcode> and plugins have an additional naming convention whereby the plugin name is added to the filename: \u003Ccode>pluginname-fr_FR.po\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>That is, the plugin name name must be the language code followed by an underscore, followed by a code for the country (in uppercase). If the encoding of the file is not UTF-8 then the encoding must be specified.\u003C\u002Fp>\n\u003Cp>For example:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>en_US – US English\u003C\u002Fli>\n\u003Cli>en_UK – UK English\u003C\u002Fli>\n\u003Cli>es_ES – Spanish from Spain\u003C\u002Fli>\n\u003Cli>fr_FR – French from France\u003C\u002Fli>\n\u003Cli>zh_CN – Simplified Chinese\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A list of language codes can be found \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FISO_639\" rel=\"nofollow ugc\">here\u003C\u002Fa>, and country codes can be found \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FISO_3166-1_alpha-2\" rel=\"nofollow ugc\">here\u003C\u002Fa>. A full list of encoding names can also be found at \u003Ca href=\"http:\u002F\u002Fwww.iana.org\u002Fassignments\u002Fcharacter-sets\" rel=\"nofollow ugc\">IANA\u003C\u002Fa>.\u003C\u002Fp>\n","Adds the JSON-LD schema.org markup for the \"Google Sitelinks Search Box\" on the homepage.",2000,49633,100,6,"2026-02-01T16:12:00.000Z","6.9.4","3.0.1","",[20,21,4],"google-sitelinks","google-sitelinks-search-box","http:\u002F\u002Fapasionados.es","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsitelinks-search-box.1.5.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},28,60790,94,326,75,"2026-04-04T15:38:00.790Z",[36],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":24,"num_ratings":24,"last_updated":46,"tested_up_to":47,"requires_at_least":17,"requires_php":18,"tags":48,"homepage":52,"download_link":53,"security_score":54,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"pryc-wp-google-sitelinks-search-box-snippest","PRyC WP: Google Sitelinks Search Box snippest","1.0.7","Patryk","https:\u002F\u002Fprofiles.wordpress.org\u002Fprycpl\u002F","\u003Cp>Plugin add to homepage code required to activate new Sitelinks Search Box @ Google search.\u003C\u002Fp>\n\u003Cp>See more: https:\u002F\u002Fdevelopers.google.com\u002Fwebmasters\u002Frichsnippets\u002Fsitelinkssearch\u003C\u002Fp>\n","Plugin add to homepage code required to activate new Sitelinks Search Box @ Google search",40,2519,"2023-06-20T11:44:00.000Z","6.2.9",[49,50,4,51],"google","google-search","wordpress","http:\u002F\u002FPRyC.pl","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpryc-wp-google-sitelinks-search-box-snippest.zip",85,{"attackSurface":56,"codeSignals":73,"taintFlows":84,"riskAssessment":85,"analyzedAt":91},{"hooks":57,"ajaxHandlers":69,"restRoutes":70,"shortcodes":71,"cronEvents":72,"entryPointCount":24,"unprotectedCount":24},[58,64],{"type":59,"name":60,"callback":61,"file":62,"line":63},"action","plugins_loaded","ap_slsb_load_textdomain","sitelinks-search-box.php",30,{"type":59,"name":65,"callback":66,"priority":67,"file":62,"line":68},"wp_head","ap_slsb_output_jsonld",20,72,[],[],[],[],{"dangerousFunctions":74,"sqlUsage":75,"outputEscaping":77,"fileOperations":24,"externalRequests":24,"nonceChecks":24,"capabilityChecks":24,"bundledLibraries":83},[],{"prepared":24,"raw":24,"locations":76},[],{"escaped":24,"rawEcho":78,"locations":79},1,[80],{"file":62,"line":81,"context":82},67,"raw output",[],[],{"summary":86,"deductions":87},"The security posture of the \"sitelinks-search-box\" v1.5 plugin appears to be strong based on the provided static analysis and vulnerability history. There are no identified entry points into the application without authentication checks, no dangerous functions, and all SQL queries are handled using prepared statements. This indicates good development practices regarding common attack vectors. The absence of file operations, external HTTP requests, and the careful handling of data flow through taint analysis further bolster this positive assessment.  Furthermore, the plugin has no recorded vulnerabilities, including critical or high severity ones, and no history of unpatched issues, suggesting a well-maintained and secure codebase.\n\nHowever, a significant concern arises from the output escaping analysis. With one total output and 0% properly escaped, this represents a clear risk of Cross-Site Scripting (XSS) vulnerabilities. Any data outputted by the plugin without proper sanitization can be exploited by attackers to inject malicious scripts into the user's browser. While the plugin exhibits strengths in data handling and entry point security, this lack of output escaping is a critical weakness that needs immediate attention.  The absence of nonce and capability checks also, while not directly flagged in the provided data, could be a potential concern if any of the (currently zero) entry points were to be introduced in future updates without proper security controls.  In conclusion, the plugin is secure in many areas but suffers from a critical flaw in output sanitization.",[88],{"reason":89,"points":90},"Output is not properly escaped",8,"2026-03-16T18:32:17.114Z",{"wat":93,"direct":98},{"assetPaths":94,"generatorPatterns":95,"scriptPaths":96,"versionParams":97},[],[],[],[],{"cssClasses":99,"htmlComments":100,"htmlAttributes":101,"restEndpoints":102,"jsGlobals":103,"shortcodeOutput":104},[],[],[],[],[],[105,106],"\u003Cscript type=\"application\u002Fld+json\">\n","\u003C\u002Fscript>\n"]