[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fZTykOHXOtMNHNGHV1MqkMiAmyxajwtB9zDhg3T9N4S8":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"parakeet","https:\u002F\u002Fprofiles.wordpress.org\u002Fparakeet\u002F",1,0,85,30,84,"2026-04-05T17:21:33.463Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":7,"num_ratings":7,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":28,"download_link":29,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":30,"fetched_at":31},"context-term-tidier","Context Term Tidier","1.0.0","\u003Cp>Many WordPress installs suffer from cramming hundreds or thousands of varied taxonomy terms in to a limited number of ill-suited, all-purpose taxonomies (eg. the default “categories” and “tags”).\u003C\u002Fp>\n\u003Cp>These are better off split in to dedicated taxonomies. For example, storing “Bill Gates” and “Microsoft” terms in “tags” is not optimal, because one is a \u003Cem>person\u003C\u002Fem> whilst the other is a \u003Cem>company\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>There is no straightforward way to split up existing taxonomies more granularly in this way, except for  labour-intensive and manual, technical effort. So, many WordPress installs continue to suffer from not having created granular taxonomies intentionally at the outset.\u003C\u002Fp>\n\u003Cp>Term Tidier tidies up messy taxonomies like these automatically. It uses natural language processing and knowledge graph technology to determine the real \u003Ca href=\"https:\u002F\u002Fgcloud.readthedocs.io\u002Fen\u002Flatest\u002F_modules\u002Fgoogle\u002Fcloud\u002Flanguage\u002Fentity.html#EntityType\" rel=\"nofollow ugc\">entity type\u003C\u002Fa> of existing terms, then re-assigns them each to a more appropriate, alternative taxonomy.\u003C\u002Fp>\n\u003Ch3>How it works\u003C\u002Fh3>\n\u003Cp>Term Tidier uses Google Cloud’s Natural Language Processing features via API calls.\u003C\u002Fp>\n\u003Cp>Users set a “source taxonomy”, the taxonomy they want to be tidied up.\u003C\u002Fp>\n\u003Cp>For each term within that taxonomy, Term Tidier calls Google Cloud to examine the term name, aiming to return a determination as to its true “entity”.\u003C\u002Fp>\n\u003Cp>The plugin receives one of eight “entity” type determinations from Google Cloud – UNKNOWN, PERSON, LOCATION, ORGANIZATION, EVENT, WORK_OF_ART, CONSUMER_GOOD or OTHER.\u003C\u002Fp>\n\u003Cp>For each entity type, users specify a target taxonomy to which a matching term will be moved. For example, you can map all terms found to be a “LOCATION” to your own “Places” taxonomy, if it exists.\u003C\u002Fp>\n\u003Cp>For each term in the source taxonomy, if a particular entity was determined, Term Tidier moves the term to your corresponding taxonomy.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Use Term Tidier from the WordPress Tools menu (Tools > Context Term Tidier).\u003C\u002Fp>\n\u003Cp>The plugin page confirms your settings as set in Settings, displaying the taxonomy and terms which will be examined.\u003C\u002Fp>\n\u003Cp>Click the “Tidy Terms” button to execute the operation.\u003C\u002Fp>\n\u003Cp>Term Tidier will cycle through each term, seeking an “entity” determination and re-assigning any terms possible.\u003C\u002Fp>\n","Tidies taxonomies that contain a mess of unrelated terms by using AI to move terms to more appropriate taxonomies.",969,"2019-10-13T13:27:00.000Z","5.2.24","3.1.0","5.2",[25,26,27],"tags","taxonomies","terms","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontext-term-tidier.zip",null,"2026-03-15T15:16:48.613Z"]