{"id":5972,"date":"2023-01-14T14:37:37","date_gmt":"2023-01-14T14:37:37","guid":{"rendered":"https:\/\/uxwritinghub.com\/?p=5972"},"modified":"2023-07-21T04:47:15","modified_gmt":"2023-07-21T04:47:15","slug":"error-message-examples","status":"publish","type":"post","link":"https:\/\/uxwritinghub.com\/error-message-examples\/","title":{"rendered":"Best 10 Examples And Guidelines For Error Messages"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"5972\" class=\"elementor elementor-5972\">\n\t\t\t\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-59db033d elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"59db033d\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-3d07cf18\" data-id=\"3d07cf18\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t\t\t<div class=\"elementor-element elementor-element-cf9fdc8 elementor-widget elementor-widget-text-editor\" data-id=\"cf9fdc8\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p>A big part of UX is about\u00a0<strong>managing pain points<\/strong>\u00a0for users. One of the most dreaded (for users) is the error message. This could be an inline error when signing up for a product or it could be one that pops up in the middle of a user\u2019s workflow. The key is to\u00a0<strong>make the interaction as smooth and painless for users as possible.<\/strong>\u00a0Microcopy best practices and <a href=\"https:\/\/uxwritinghub.com\/content-style-guides\/\">style guides<\/a> can help you when crafting these types of messages but there\u2019s a lot more to them than just the basics.\u00a0<\/p>\n<p>Here are ten basic guidelines to help <a href=\"https:\/\/uxwritinghub.com\/what-is-ux-writing\/\">UX writers<\/a> and <a href=\"https:\/\/uxwritinghub.com\/the-rise-of-content-design\/\">content designers<\/a> create the most effective error messaging for your users.<\/p>\n<p>\ud83e\uddd9\u200d\u2642\ufe0f Want to have a go at creating error messages and other microcopy? <a href=\"https:\/\/course.uxwritinghub.com\/free_course\">Try our free course A Taste of UX Writing<\/a><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-a0e555f elementor-toc--minimized-on-tablet elementor-widget elementor-widget-table-of-contents\" data-id=\"a0e555f\" data-element_type=\"widget\" data-settings=\"{&quot;headings_by_tags&quot;:[&quot;h2&quot;],&quot;exclude_headings_by_selector&quot;:[],&quot;marker_view&quot;:&quot;numbers&quot;,&quot;minimize_box&quot;:&quot;yes&quot;,&quot;minimized_on&quot;:&quot;tablet&quot;,&quot;hierarchical_view&quot;:&quot;yes&quot;,&quot;min_height&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:[]},&quot;min_height_tablet&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:[]},&quot;min_height_mobile&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:[]}}\" data-widget_type=\"table-of-contents.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"elementor-toc__header\">\n\t\t\t<div class=\"elementor-toc__header-title\">\n\t\t\t\tTable of Contents\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-toc__toggle-button elementor-toc__toggle-button--expand\"><svg class=\"e-font-icon-svg e-fas-chevron-down\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M207.029 381.476L12.686 187.132c-9.373-9.373-9.373-24.569 0-33.941l22.667-22.667c9.357-9.357 24.522-9.375 33.901-.04L224 284.505l154.745-154.021c9.379-9.335 24.544-9.317 33.901.04l22.667 22.667c9.373 9.373 9.373 24.569 0 33.941L240.971 381.476c-9.373 9.372-24.569 9.372-33.942 0z\"><\/path><\/svg><\/div>\n\t\t\t\t<div class=\"elementor-toc__toggle-button elementor-toc__toggle-button--collapse\"><svg class=\"e-font-icon-svg e-fas-chevron-up\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M240.971 130.524l194.343 194.343c9.373 9.373 9.373 24.569 0 33.941l-22.667 22.667c-9.357 9.357-24.522 9.375-33.901.04L224 227.495 69.255 381.516c-9.379 9.335-24.544 9.317-33.901-.04l-22.667-22.667c-9.373-9.373-9.373-24.569 0-33.941L207.03 130.525c9.372-9.373 24.568-9.373 33.941-.001z\"><\/path><\/svg><\/div>\n\t\t\t\t\t<\/div>\n\t\t<div class=\"elementor-toc__body\">\n\t\t\t<div class=\"elementor-toc__spinner-container\">\n\t\t\t\t<svg class=\"elementor-toc__spinner eicon-animation-spin e-font-icon-svg e-eicon-loading\" aria-hidden=\"true\" viewBox=\"0 0 1000 1000\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M500 975V858C696 858 858 696 858 500S696 142 500 142 142 304 142 500H25C25 237 238 25 500 25S975 237 975 500 763 975 500 975Z\"><\/path><\/svg>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7a1608d0 elementor-widget elementor-widget-text-editor\" data-id=\"7a1608d0\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<p><!-- wp:paragraph --><\/p>\n<h2><span style=\"color: inherit; font-family: inherit; font-size: 2rem;\">1. Keep language clear and concise<\/span><\/h2>\n<p>The rule that applies to all <a href=\"https:\/\/uxwritinghub.com\/what-is-microcopy\/\">UX microcopy<\/a> also applies to error messaging. The longer a message, the less likely your users will read them. In fact, an <a href=\"http:\/\/prsay.prsa.org\/2009\/01\/14\/how-to-make-your-copy-more-readable-make-sentences-shorter\/\" target=\"_blank\" rel=\"noopener\">oft-cited study<\/a> by the American Press Institute showed that shorter sentences results in greater understanding by users. So, when sentences were 14 words or less, users understood 90% of the messaging. When the sentences were <strong>8 words or less, users understood the whole 100%.<\/strong><\/p>\n<p>Now, sometimes it might not be possible to write a message that short, so don\u2019t beat yourself up attempting to get to 8 words on your error popup. Just remember that less is more and clarity and usefulness are the most important things.<\/p>\n<p>For example, don\u2019t do:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img style=\"width: 500px;\" src=\"https:\/\/lh6.googleusercontent.com\/HmWWmyrOSCTaOGr08BPg2HYf8_RAEzZV0rypuO-QjEI1R3Q5_xBCWawbpUfwlSdyZO3hZxGEMlq0qoRenqa0cbDXvdctE1AMR7J4PBLwTB9k6kiZEK5x1INkNKeCHvYMljrrkIY0\" alt=\"generic error message by Instagram\" width=\"500\" height=\"859\" \/><br \/><em>Sure, it\u2019s a short message but does it tell users anything at all?<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>Instead, this works better:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:image {\"width\":320,\"height\":569} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh3.googleusercontent.com\/mvz2gXrf9kyFFq69MzY5M2ZzxO3Tp-n1bxxltqb7kRhOOzKglh3QryCPa4TDuMolPvyetcrYGc6ci1r1NXmoeGviypU7IxgPgXaYM1C02Xn-r_VccZGzJzPFHx7czxo3j6xtNY66\" alt=\"we have a little problem error message by Spotify\" width=\"320\" height=\"569\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>Clear, concise, and empathetic messaging from Spotify. Users know what the problem is and what they need to do to fix it.<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":2} --><\/p>\n<h2>2. Keep user actions specific and logical<\/h2>\n<p>The action buttons for your error messages should be very clear to users. Even if they don\u2019t read the whole error message, they should be able to easily see <strong>which option to choose in order to solve the issue<\/strong>. If the error message has a \u201cyes,\u201d \u201cno,\u201d or \u201ccancel\u201d action button, consider adding an action word after it. \u201cYes, refresh the page.\u201d or \u201cNo, stay in the app.\u201d<\/p>\n<p>Within the error message itself, there should also be the consequences of those actions. If they stay in the app or refresh instead, what will happen to their progress thus far? Make sure everything is explained as simply and clearly as possible.\u00a0<\/p>\n<p>Please, don\u2019t do this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image --><\/p>\n<figure class=\"wp-block-image\"><img src=\"https:\/\/lh5.googleusercontent.com\/sA0rX2YcgoKrQVSrAdwU1lcIs_NqWA21vF1a58gsyfotWbux_phV76DNhsYbkIhBX-ASe9S_V8aPabpN0xaxqAg86Sby7A0chOkP3Y4aXY0BlWE1Pi_unzDp0KSc63TVP8X60leS\" alt=\"task is still in progress error message\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>I feel like these are trick buttons for users.<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>Rather, this is much clearer:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh6.googleusercontent.com\/z6yBKBimOpJOAGtyeqaK2rR6__5zswPEScp751hMlhwx11UAfmSMj4c9FFeXYS2f1dV5Uw3zBvfhTynyVIn2MGxKkiDbZSbeZtxl15z9jBTdmXMlFCuBBIbhPRREc_3vPA4glM3n\" alt=\"Instagram gives users two clear actions that go along with the message above them\" width=\"318\" height=\"277\" \/><br \/><em>Instagram gives users two clear actions that go along with the message above them.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":3} --><\/p>\n<h2>3. Avoid oops and whoops<\/h2>\n<p>The Internet has come a long way from those original \u201cOops!\u201d messages. Users have been oopsed and whoopsed to death at this point, so <strong>generally it\u2019s best to avoid the cutesy sounding language<\/strong>.\u00a0<\/p>\n<p>It doesn\u2019t really help smooth anything over for users any more and might even annoy them. Would you say whoops to your manager or to a professional colleague if you made an error? Probably not.\u00a0<\/p>\n<p>It\u2019s generally not good business to talk to your users like they\u2019re children or baby internet users either. At this point, they\u2019ve probably seen error messages and realize what their purpose is, so the \u201coops\u201d is no longer necessary. (Some people might also throw \u201cyikes\u201d in that group as well but this can also depend on your brand\u2019s tone and voice.)<\/p>\n<p>Please, don\u2019t do:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image --><\/p>\n<figure class=\"wp-block-image\"><img src=\"https:\/\/lh4.googleusercontent.com\/hR-BTQz90RwyCkgUoOPTZvCpAOwv3NVY_d1rUE8bqTnNr99iz8NAgIJRgNoarxxDcc38tCNF_eW7bZDsrIGhnE9YFRf7IHxjQ-uXDjdwGnUtZIBqb-klA1Be3DueKr7aPdufsEw5\" alt=\"whiipsie daize error message\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>So many things wrong with this one. What if your users aren\u2019t native English speakers? Also, what happened to using periods at the end of sentences?<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>This is much better:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh5.googleusercontent.com\/34xppLOgC8SNz_dQsUFWUBmzOf4odC6snmWSdz4UcmIO0QDRRgtykGfqm7hZDlGJLZlEO-z2NBgK-6gJiPVojaIrvenEEg9abgfyPt10yJsmSFyg4R6MCwQtnA9VNp9Bf1R3g4rK\" alt=\"Twitch\u2019s error messaging is on brand, a little humorous, but not cutesy or annoying\" width=\"344\" height=\"176\" \/><br \/><em>Twitch\u2019s error messaging is on brand, a little humorous, but not cutesy or annoying.<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":4} --><\/p>\n<h2>4. Don\u2019t blame the user<\/h2>\n<p>Users are already going to be frustrated when they get an error message\u2014don\u2019t make it worse by placing the blame on them. This means you should avoid using phrases like \u201cyou did\u201d or \u201cyou didn\u2019t\u201d when explaining what went wrong. Instead, <strong>keep directives specific to what the user needs to do to<\/strong> remedy the problematic action. If the email address they entered is incorrect, then say \u201cPlease enter a valid email address using the following format: joe@example.com\u201d instead of telling the user: \u201cYou entered your email incorrectly.\u201d\u00a0<\/p>\n<p>Don\u2019t do this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image {\"width\":537,\"height\":248} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh5.googleusercontent.com\/O4VBiP-oCRx5UvuflGVmewsW05B1yvegkcRqGe9CgRXfr-nrHzdgc3nbFeu7s7a0aSuSFHGfZ0GRrX5WJkt7_Q9uqLUpP39JF9YwBAYWItCJDRxvqBxTmbLpn5NGrKjDKQX6qz9R\" alt=\"unclear error message\" width=\"537\" height=\"248\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>I feel like I\u2019m in trouble and I don\u2019t even know why.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>This works much better:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:image {\"width\":386,\"height\":392} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh3.googleusercontent.com\/voxRlVN3ouWRbgtQmaeibOEX92-zfGE4kP7dnUUME-yae_gOABvF0c8Ikk6az3a1dhpivId2pjs-2P9yuHNW_hepP3zvLp-o91WekOFH9oboaE9DJbySZVyV_jswU8AykpAf7P76\" alt=\"HBOMax demonstrating the correct format needed rather than telling me I did it wrong.\" width=\"386\" height=\"392\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>HBOMax demonstrating the correct format needed rather than telling me I did it wrong.\u00a0\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":5} --><\/p>\n<h2>5. Avoid ambiguity<\/h2>\n<p>How many times have you gotten frustrated at an error message that popped up with nothing helpful anywhere? We all have been there. Try to keep your users from wanting to shout at the screen by being specific about the error. No, that doesn\u2019t mean you need to put a long jargon-heavy error code. That won\u2019t mean anything to the user. Instead tell them <strong>why there was an error and how they can address the issue.\u00a0<\/strong><\/p>\n<p>Avoid vague messaging like this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image --><\/p>\n<figure class=\"wp-block-image\"><img title=\"Facebook_error\" src=\"https:\/\/lh6.googleusercontent.com\/yhlrJ7HW1Z5SDGJpwtmqOZLH-ljYhfc_SXFJ7ABILms5KjroYeZxyk4xtkJmGy3O2SLnfeKwxIEr-tR7ttBCZrqVmq2gKHBKutA50hcHhGW03Wpi7gth8SnbYhgQsXdISXHkXMDa\" alt=\"Facebook Error\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p style=\"padding-left: 40px;\">Instead, keep it specific, like this:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:image {\"width\":410,\"height\":482} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh6.googleusercontent.com\/0HbW_zotlnxxzWg60d9lRLeWK2ULLWtIXlsXZBt4SL9-co6OV8gCI83-x1qYsI2LxsCUGCm_SCM0RCbcxXImw2Sn0Jinns59MnWtQ2Kb-Ipw-ILJPbAlYsFEDZcxNaM_64COSM-Q\" alt=\"Slack is known for having great (and appropriately humorous) microcopy.\" width=\"410\" height=\"482\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>Slack is known for having great (and appropriately humorous) <\/em><a href=\"https:\/\/www.facebook.com\/photo?fbid=883058615625101&amp;set=gm.1579018679154148\"><em>microcopy<\/em><\/a><em>.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":6} --><\/p>\n<h2><strong>6. Don\u2019t mock your users \/ Keep the jokes to a minimum<\/strong><\/h2>\n<p>No one likes being talked down to. Unfortunately, a lot of \u201chumor\u201d found online and in UX can come across as condescending. There are lots of other places to inject friendly, light humor into UX microcopy but an error message isn\u2019t always the best place for it. It would be like asking a friend for advice about your bad day and then they make a sarcastic comment instead. Not the best way to keep user stress levels low.<\/p>\n<p><a href=\"https:\/\/styleguide.mailchimp.com\/\" target=\"_blank\" rel=\"noopener\">Mailchimp\u2019s style guide<\/a> lays it out more specifically, \u201cdon\u2019t go out of your way to make a joke \u2014 forced humor can be worse than none at all. <strong>If you\u2019re unsure, keep a straight face<\/strong>.\u201d (Check out <a href=\"https:\/\/uxwritinghub.com\/content-style-guides\/\">more style guides<\/a> for notes on humor and jokes in microcopy.)<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><\/p>\n<p style=\"padding-left: 40px;\">Best to not do this:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh3.googleusercontent.com\/AbTFPhMU38Jo8o4WFApIUlgXdeh5t7bWj1f3jtwufIIzy239K5iB5-XdWMtYjpql8COXJNHv-BJ76yCXk-aEBJunoiJti45_vzAVHaRBACdk1wWj8Zh0sYaqM59M1KplQvdt2mVC\" alt=\"A perfectly unnecessary example of condescending microcopy on an unsubscribe link.\" width=\"624\" height=\"147\" \/><br \/><em>A perfectly unnecessary <\/em><a href=\"https:\/\/www.facebook.com\/photo?fbid=10160404650933368&amp;set=gm.1593355277720488\" target=\"_blank\" rel=\"noopener\"><em>example<\/em><\/a><em> of condescending microcopy on an unsubscribe link.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>Instead, humor can be used to have a little fun when appropriate:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh4.googleusercontent.com\/gIONVsFDCSccv-5wwAb7d8gJ_WSfg4TV07VSz388sqc7DhsHcgDHJzbkC61mnilzEcaGttN_e4dscWn3It08Eu5DzUSeMftDLTBhS1NQMRuTDKsdBaNh8wc4fDWBXzpI4EuVAICP\" alt=\"on brand error message\" width=\"481\" height=\"307\" \/><br \/><em>This is on brand and a tiny bit silly but it still made me chuckle. (For more great examples of 404 pages done well, check out <\/em><a href=\"https:\/\/uxdesign.cc\/10-examples-of-custom-404-pages-ranked-from-best-to-worst-9c74825c18c9\" target=\"_blank\" rel=\"noopener\"><em>ten examples here<\/em><\/a><em> and even more <\/em><a href=\"https:\/\/www.creativebloq.com\/web-design\/best-404-pages-812505\/2\" target=\"_blank\" rel=\"noopener\"><em>here<\/em><\/a><em>.)<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":7} --><\/p>\n<h2>7. Avoid negative words<\/h2>\n<p>This goes along with user blaming and condescending language. The user is already going to be experiencing some levels of stress because, well, they\u2019re getting an error message.\u00a0<\/p>\n<p>This should be <strong>an opportunity to positively inform users about errors<\/strong> rather than reinforce a negative interaction. It\u2019s a simple language adjustment that can really help users breathe a little easier. Some style guides, like Apple\u2019s, prefer a friendly tone over choosing positive words so check with your company\u2019s <a href=\"https:\/\/uxwritinghub.com\/ux-content-guides\/\">style guide<\/a> to be sure.<\/p>\n<p>Please, please don\u2019t do this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image {\"width\":409,\"height\":375} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh6.googleusercontent.com\/QSANEk40XU_3NTi3Phqd0Tu2bSYvVY-ru_K0BjrrhxejQkCCzUPiVRWntwUkgYvHJZ12QefXLiMkp00Y3jTQLQIc610CJRxyOrQv8cMAr4j4Lr9nPGQuKRoEOkdNOcNyol99hFQW\" alt=\"nope. try again error message example\" width=\"409\" height=\"375\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>Not only is this microcopy from Bitly negative, it comes across as condescending and doesn\u2019t tell the user what is wrong with the password OR the email format. \ud83d\ude20<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>This is much, much better:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh3.googleusercontent.com\/akd11Jwf_VOUS46jfdBpV4TuquTMYIdB8vIZY4xB0jz7pe0qrihESCzo9cMgVTM7iekr3VRfBK8pXJt9sssVDYXd1RNGsHKOHad0Hn9uw4ewBIBGMglOySKOmWv5WMGjm6i0ODro\" alt=\"somthing went wrong\" width=\"490\" height=\"300\" \/><br \/><em>Microsoft Office taking the blame and telling users what to do next without any negative words directed at them.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":8} --><\/p>\n<h2>8. Write for humans<\/h2>\n<p>No one wants to get one of those Windows messages with a file name three lines long. (What does GeneralNetworkUserError_502 mean anyway?) UX microcopy is all about <strong>connecting with users and providing a good experience<\/strong> for them, not bombarding them with technical jargon that they won\u2019t understand (And probably will not help them solve the issue that led to the error in the first place.)<\/p>\n<p>This is one of those universal microcopy rules that applies to all messaging. Write like you\u2019re a human, not a jargon robot. (If you need to include more information about a particular error, then add in a drop down that the user can opt to click should they want to learn more about Error 502.)<\/p>\n<p>Definitely don\u2019t do this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh5.googleusercontent.com\/kAJBeNSgAMeE49i9ZuWWwSa1ANqFnHonObsMJkWG9J3efQq_k7zw7HTOKzSGOx5lSTz5cxbkaSlNBMOvjxsZLTuyfuF5gL8oSEeMpCVHSmG8y3ckIAr8nrPchx67e98jVrS4H5pW\" alt=\"define error message for security id\" width=\"478\" height=\"246\" \/><br \/><em>Umm, what does that error message even mean?<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>Instead, do this:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:image {\"width\":491,\"height\":323} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh5.googleusercontent.com\/bG6bKjZ_mhbAQMuvLAqJ-SIdHCOvkSZ72XT7sJOTDxHWQmD41Ho9KwI5kmQBoAVltK2e07N8elHTW9P_74mtkNER2mfPw3y725aZcu86XKhl5041gzFXtyEC4ADLgEb-MPIQMhhN\" alt=\"the email and password do not match our records\" width=\"491\" height=\"323\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>Straight to the point and in simple language that sounds like an actual person is talking.<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:image {\"width\":354,\"height\":264} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh5.googleusercontent.com\/aQahIUNiX0Itmk9lMoBP_vkmvkk2oLrgaw3V1g_Ve6QCnPEZ78-d-ylldweTVbhzZUF_BzKo-rqzlK64Q0KbyQ-Q4O0gjzezeg7B77MD9xnFIoWpSG5DrC0LHVTHgutstsjN0bn-\" alt=\"another user has the same name. Maybe it's your eveil twin spooky\" width=\"354\" height=\"264\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:list {\"ordered\":true,\"start\":9} --><\/p>\n<h2>9. Don\u2019t write in ALL CAPS (and avoid exclamation marks)<\/h2>\n<p>Everyone knows that one person who sends them messages in all caps. And we all should know that typing in all caps is basically <strong>like shouting in real life.<\/strong> As are exclamation points. Now, I love to use exclamation points all the time in my emails but when it comes to mircoropy or content, it\u2019s mostly a big \u201cno.\u201d They can add stress or anxiety when it\u2019s completely avoidable by just not using them.<\/p>\n<p>Don\u2019t do this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image {\"width\":331,\"height\":362} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh5.googleusercontent.com\/IrXMjT1sGXE1H5CPuFmAC9jqN-KXz8kNUlxAttmZOdYr0sICaPGOBLfzvvDTBFbBSo5sPV1uHAJnAV1Xo70WbssJuvmE9EFiDobGS3qxYRXRh32xBG68REuAPOGl1lPt2pwVbQhH\" alt=\"message with an exlemation point in a game\" width=\"331\" height=\"362\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>(Yes, I know this is from a game. I\u2019ve talked about <\/em><a href=\"https:\/\/uxwritinghub.com\/mobile-games-microcopy\/\"><em>microcopy in games<\/em><\/a><em> before.) But still, when everything has an exclamation point, users really don\u2019t know which buttons are important.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>If you really <s>have to<\/s> want to use an exclamation point, do it like this:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:image --><\/p>\n<figure class=\"wp-block-image\"><img src=\"https:\/\/lh3.googleusercontent.com\/QnazFYT9JP5SsUwRY67l9uuHIM92XVbv59SXsrmDATzYO7pE4FuUmjmT3Zz8WBTZEOSoODIp_r8ydRXUGX4OeN8aMVHh1J0DkhutaWPro97nHq5UqmMBw7wKI8zJQWLSbMjzHiDh\" alt=\"unexpected things will happen if you wouldn't read this\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>Github is trying to bring attention to the message with the yellow highlight and very light usage of that exclamation point. There\u2019s a bit of humor injected so users don\u2019t feel like they\u2019re being shouted at.<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:list {\"ordered\":true,\"start\":10} --><\/p>\n<h2>10. Try to use inline validation<\/h2>\n<p>This guideline is less about microcopy and more about UX design. Rather than having an error message pop up with a long list of things the user needs to complete, it\u2019s much better UX to have inline validation. Inline validation is basically <strong>putting the error message right next to or above the label it belongs with.<\/strong> This also assists with accessibility as screen readers should read the error message and the field label together, allowing all users to better address the issue at hand.\u00a0<\/p>\n<p>This really is the worst possible way to do this:<\/p>\n<p><!-- \/wp:list --><!-- wp:paragraph --><!-- \/wp:paragraph --><!-- wp:image {\"width\":342,\"height\":607} --><\/p>\n<figure class=\"wp-block-image is-resized\"><img src=\"https:\/\/lh3.googleusercontent.com\/LNtFZmsaGLrRMnmNJtC5PG9GeE0yqgwwRPvbpvpVIP9UitrgH6AWpZjhSlNuymWH6c64t-kAjifFU1OD6URyj2nFF2ZH4N8fV0Bw1zG-aI5RBwSOqT7ZWcuahVI22Uj1Nnz4uoFq\" alt=\"list of many error messages\" width=\"342\" height=\"607\" \/><\/figure>\n<p><!-- \/wp:image --><!-- wp:paragraph --><\/p>\n<p><em>Giving users a long list is only going to frustrate them further and make it extremely difficult to understand, especially users with screen readers.<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p>Please make life better for all users by doing this:<\/p>\n<p><!-- \/wp:paragraph --><!-- wp:paragraph --><\/p>\n<p><img src=\"https:\/\/lh5.googleusercontent.com\/00U-VArEkJj8uEJ4VVNefcTawseNb5N6ZaxIn3ejRi5MAMGPUSND1auFiAQufmngbEjQV6n14B-1ABCAoq3wHDZlLJTx0fSYrsof_2qd0w1GlwEQvG4Z_zw52aV11mNxNCWAIOCj\" alt=\"seperated error messages\" width=\"369\" height=\"271\" \/><br \/><em>Hulu showing that inline validation is becoming standard across the Internet and apps because it\u2019s a much better experience for users.\u00a0<\/em><\/p>\n<p><!-- \/wp:paragraph --><!-- wp:separator --><\/p>\n<hr class=\"wp-block-separator\" \/>\n<p><!-- \/wp:separator --><!-- wp:paragraph --><\/p>\n<p>Do you agree with our guidelines or do you think something is missing?\u00a0<br \/>I\u2019d love to hear more. You can find me on <a href=\"https:\/\/www.linkedin.com\/in\/meglong\/\" target=\"_blank\" rel=\"noopener\">LinkedIn<\/a>; I love chatting about words. The UX and Microcopy <a href=\"https:\/\/www.facebook.com\/groups\/microcopy\" target=\"_blank\" rel=\"noopener\">Facebook group<\/a> is into discussing all sorts of microcopy. Come and join the discussion!<\/p>\n<h2>Keep learning<\/h2>\n<p><a href=\"https:\/\/uxwritinghub.com\/what-is-ux-writing\/\">What is UX writing?<\/a> (article)<br \/><br \/><a href=\"https:\/\/uxwritinghub.com\/what-is-microcopy\/\">Microcopy in a nutshell<\/a> (article)<br \/><br \/><a href=\"https:\/\/uxwritinghub.com\/ux-writing-vs-content-design\/\">UX writing vs. content design: Setting the record straight<\/a> (article and podcast episode)<br \/><br \/><a href=\"https:\/\/uxwritinghub.com\/ux-research-for-beginners\/\">UX research for beginners<\/a> (article)<br \/><br \/><a href=\"https:\/\/uxwritinghub.com\/whos-afraid-of-ux-research-with-dr-natalya-sarana-flixbus\/\">Who&#8217;s afraid of UX research?<\/a> (podcast episode)<\/p>\n<p><!-- \/wp:paragraph --><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Here are ten basic guidelines to help you create the most effective error messaging for your users.<\/p>\n","protected":false},"author":14,"featured_media":5977,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tpgb_global_settings":"","_eb_attr":"","content-type":"","_mi_skip_tracking":false},"categories":[59],"tags":[],"acf":{"descriptions":false},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v19.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Best 10 Examples And Guidelines For Error Messages<\/title>\n<meta name=\"description\" content=\"Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of them!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/uxwritinghub.com\/error-message-examples\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Best 10 Examples And Guidelines For Error Messages\" \/>\n<meta property=\"og:description\" content=\"Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of them!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/uxwritinghub.com\/error-message-examples\/\" \/>\n<meta property=\"og:site_name\" content=\"UX WRITING HUB\" \/>\n<meta property=\"article:published_time\" content=\"2023-01-14T14:37:37+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-07-21T04:47:15+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png\" \/>\n\t<meta property=\"og:image:width\" content=\"904\" \/>\n\t<meta property=\"og:image:height\" content=\"504\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Meg Long\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Meg Long\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/uxwritinghub.com\/#website\",\"url\":\"https:\/\/uxwritinghub.com\/\",\"name\":\"UX WRITING HUB\",\"description\":\"Learn to write user experience\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/uxwritinghub.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/uxwritinghub.com\/error-message-examples\/#primaryimage\",\"url\":\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png\",\"contentUrl\":\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png\",\"width\":904,\"height\":504},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/uxwritinghub.com\/error-message-examples\/#webpage\",\"url\":\"https:\/\/uxwritinghub.com\/error-message-examples\/\",\"name\":\"Best 10 Examples And Guidelines For Error Messages\",\"isPartOf\":{\"@id\":\"https:\/\/uxwritinghub.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/uxwritinghub.com\/error-message-examples\/#primaryimage\"},\"datePublished\":\"2023-01-14T14:37:37+00:00\",\"dateModified\":\"2023-07-21T04:47:15+00:00\",\"author\":{\"@id\":\"https:\/\/uxwritinghub.com\/#\/schema\/person\/f55525eefa939e1791fd954d5c42756b\"},\"description\":\"Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of them!\",\"breadcrumb\":{\"@id\":\"https:\/\/uxwritinghub.com\/error-message-examples\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/uxwritinghub.com\/error-message-examples\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/uxwritinghub.com\/error-message-examples\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/uxwritinghub.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Best 10 Examples And Guidelines For Error Messages\"}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/uxwritinghub.com\/#\/schema\/person\/f55525eefa939e1791fd954d5c42756b\",\"name\":\"Meg Long\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/uxwritinghub.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-96x96.jpg\",\"contentUrl\":\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-96x96.jpg\",\"caption\":\"Meg Long\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Best 10 Examples And Guidelines For Error Messages","description":"Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of them!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/uxwritinghub.com\/error-message-examples\/","og_locale":"en_US","og_type":"article","og_title":"Best 10 Examples And Guidelines For Error Messages","og_description":"Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of them!","og_url":"https:\/\/uxwritinghub.com\/error-message-examples\/","og_site_name":"UX WRITING HUB","article_published_time":"2023-01-14T14:37:37+00:00","article_modified_time":"2023-07-21T04:47:15+00:00","og_image":[{"width":904,"height":504,"url":"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png","type":"image\/png"}],"author":"Meg Long","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Meg Long","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebSite","@id":"https:\/\/uxwritinghub.com\/#website","url":"https:\/\/uxwritinghub.com\/","name":"UX WRITING HUB","description":"Learn to write user experience","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/uxwritinghub.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/uxwritinghub.com\/error-message-examples\/#primaryimage","url":"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png","contentUrl":"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png","width":904,"height":504},{"@type":"WebPage","@id":"https:\/\/uxwritinghub.com\/error-message-examples\/#webpage","url":"https:\/\/uxwritinghub.com\/error-message-examples\/","name":"Best 10 Examples And Guidelines For Error Messages","isPartOf":{"@id":"https:\/\/uxwritinghub.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/uxwritinghub.com\/error-message-examples\/#primaryimage"},"datePublished":"2023-01-14T14:37:37+00:00","dateModified":"2023-07-21T04:47:15+00:00","author":{"@id":"https:\/\/uxwritinghub.com\/#\/schema\/person\/f55525eefa939e1791fd954d5c42756b"},"description":"Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of them!","breadcrumb":{"@id":"https:\/\/uxwritinghub.com\/error-message-examples\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/uxwritinghub.com\/error-message-examples\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/uxwritinghub.com\/error-message-examples\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/uxwritinghub.com\/"},{"@type":"ListItem","position":2,"name":"Best 10 Examples And Guidelines For Error Messages"}]},{"@type":"Person","@id":"https:\/\/uxwritinghub.com\/#\/schema\/person\/f55525eefa939e1791fd954d5c42756b","name":"Meg Long","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/uxwritinghub.com\/#\/schema\/person\/image\/","url":"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-96x96.jpg","contentUrl":"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-96x96.jpg","caption":"Meg Long"}}]}},"tpgb_featured_images":{"full":["https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png",904,504,false],"tp-image-grid":["https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png",700,390,false],"thumbnail":["https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49-150x150.png",150,150,true],"medium":["https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49-300x167.png",300,167,true],"medium_large":["https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49-768x428.png",768,428,true],"large":["https:\/\/uxwritinghub.com\/wp-content\/uploads\/2021\/01\/Screen-Shot-2021-01-14-at-16.36.49.png",800,446,false],"default":"https:\/\/uxwritinghub.com\/wp-content\/plugins\/the-plus-addons-for-block-editor\/assets\/images\/tpgb-placeholder.jpg"},"tpgb_post_meta_info":{"get_date":"January 14, 2023","category_list":{"category":[{"term_id":59,"name":"Best practices","slug":"content-strategy","term_group":0,"term_taxonomy_id":59,"taxonomy":"category","description":"","parent":0,"count":122,"filter":"raw"}],"post_tag":false},"author_name":"Meg Long","author_url":"https:\/\/uxwritinghub.com\/author\/meg\/","author_email":"globalmeg@gmail.com","author_website":"","author_description":"","author_facebook":"","author_twitter":"","author_instagram":"","author_role":["author"],"author_firstname":"Meg","author_lastname":"Long","user_login":"Meg","author_avatar":"<img width=\"200\" height=\"194\" src=\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg.jpg\" class=\"avatar avatar-200 photo\" alt=\"\" srcset=\"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg.jpg 668w, https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-300x291.jpg 300w, https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-24x24.jpg 24w, https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-48x48.jpg 48w\" sizes=\"(max-width: 200px) 100vw, 200px\" \/>","author_avatar_url":"https:\/\/uxwritinghub.com\/wp-content\/uploads\/2019\/09\/meg-96x96.jpg","comment_count":18,"post_likes":0,"post_views":0},"tpgb_post_category":{"category":"<a href=\"https:\/\/uxwritinghub.com\/category\/content-strategy\/\" alt=\"Best practices\" class=\"category-content-strategy\">Best practices<\/a> "},"_links":{"self":[{"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/posts\/5972"}],"collection":[{"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/comments?post=5972"}],"version-history":[{"count":2,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/posts\/5972\/revisions"}],"predecessor-version":[{"id":39182,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/posts\/5972\/revisions\/39182"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/media\/5977"}],"wp:attachment":[{"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/media?parent=5972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/categories?post=5972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/uxwritinghub.com\/wp-json\/wp\/v2\/tags?post=5972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}