{"id":262,"date":"2026-07-12T17:31:11","date_gmt":"2026-07-12T08:31:11","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/alt-text\/"},"modified":"2026-11-15T18:46:51","modified_gmt":"2026-11-15T09:46:51","slug":"alt-text","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/alt-text\/","title":{"rendered":"Alt Text"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">What is alt text?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Alt text is text placed in the <code>img<\/code> attribute of the <code>alt<\/code> tag that briefly describes an image in words. It&#8217;s often called an &#8220;alt tag.&#8221; It has three main uses.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Accessibility (the original main purpose)<\/strong> &#8211; For users who can&#8217;t see the image, screen readers (programs that read the screen aloud) read the text in <code>alt<\/code> aloud or convert it to braille.<\/li>\n\n\n\n<li><strong>Fallback when loading fails<\/strong> &#8211; If an image is broken or fails to load, the alt text appears in its place.<\/li>\n\n\n\n<li><strong>Image search<\/strong> &#8211; Google uses it as a signal to understand what the image shows.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The W3C, which sets the global web accessibility standards, specifies that every image should have alt text describing the information or function it conveys, so that people with various disabilities get the same information. This text is read aloud or converted to braille. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;img src=\"dalmatian-puppy.jpg\" alt=\"Dalmatian puppy playing fetch\"&gt;<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Not an alt &#8220;tag&#8221; but an alt &#8220;attribute&#8221;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The term &#8220;alt tag&#8221; is common in practice, but strictly speaking it isn&#8217;t accurate. The tag is <code>&lt;img&gt;<\/code>, and <code>alt<\/code> is one of several attributes inside that tag. Both Google&#8217;s official documentation and the W3C consistently call it the &#8220;alt attribute.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Since everyone understands either way, there&#8217;s no need to correct people, but the accurate name is the alt attribute.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How Google uses alt text<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Google uses <code>alt<\/code> text together with computer vision (technology that analyzes images) and the page&#8217;s content to understand what an image is about. In other words, <code>alt<\/code> is one of the key signals for understanding an image&#8217;s subject. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google doesn&#8217;t look only at <code>alt<\/code>. It also looks at the file name, surrounding text, captions and image titles. That&#8217;s why Google recommends giving files descriptive names, such as <code>IMG00023.JPG<\/code> rather than <code>my-new-black-kitten.jpg<\/code>, and placing images near related text. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The writing principle is to describe the image usefully and informatively in the context of the page, with keywords used appropriately. Conversely, Google explicitly says to avoid stuffing <code>alt<\/code> with keywords (keyword stuffing), because it hurts the user experience and can cause the site to be treated as spam. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, alt text&#8217;s effect on rankings depends on the type of search. It&#8217;s a ranking factor in Google Image Search, but not a separate ranking factor in regular web search. Google&#8217;s John Mueller said that if you don&#8217;t care about image search, you don&#8217;t need to worry much about <code>alt<\/code> from a web search perspective, and that <code>alt<\/code> isn&#8217;t a magical SEO cure-all. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/ranking-factors\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Search Engine Journal<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to write it well<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The key is finding the point that satisfies both goals, accessibility and search. John Mueller also pointed out that balancing these two aspects is the tricky part. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.searchenginejournal.com\/google-on-alt-text-seo-accessibility\/468044\/\" target=\"_blank\" rel=\"noopener\">Search Engine Journal<\/a> Following these principles solves most cases.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Be specific, but concise.<\/strong> The W3C recommends writing <code>alt<\/code> as the shortest description that conveys the image&#8217;s purpose. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/tips\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a> Using Google&#8217;s example, <code>alt=\"puppy\"<\/code> (puppy) is not as good as <code>alt=\"Dalmatian puppy playing fetch\"<\/code> (Dalmatian puppy playing fetch). <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li>\n\n\n\n<li><strong>Keep it short.<\/strong> In the industry, 125 characters or fewer is widely used. Screen reader users can&#8217;t pause and skip partway through a reading, so long text gets annoying. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Semrush<\/a><\/li>\n\n\n\n<li><strong>Don&#8217;t add prefixes like &#8220;Image:&#8221;, &#8220;Photo:&#8221; or &#8220;Icon:&#8221;.<\/strong> Screen readers and Google already know it&#8217;s an image. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/tips\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a> <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a> However, if the subject really is a printed photograph, it&#8217;s fine to say so as an exception. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Semrush<\/a><\/li>\n\n\n\n<li><strong>Don&#8217;t force keywords in.<\/strong> First describe the image accurately and specifically, and include one or two relevant keywords only when they fit the description naturally. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Semrush<\/a><\/li>\n\n\n\n<li><strong>Reflect the context.<\/strong> Even for the same image, the right alt text differs depending on the page&#8217;s purpose. <code>alt<\/code> should convey the meaning the image is meant to communicate, not just a literal account of what&#8217;s visible. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/informative\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a><\/li>\n\n\n\n<li><strong>Leave decorative images with an empty <code>alt<\/code>(<code>alt=\"\"<\/code>).<\/strong> Pure decorative images that add no information to the content should get empty alt text so screen readers skip them. If you remove the attribute entirely, some screen readers read the file name instead, so the right approach is not to delete it but to leave it empty as <code>alt=\"\"<\/code>. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/decorative\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a><\/li>\n\n\n\n<li><strong>Match the image type.<\/strong> For functional images inside links or buttons, describe the function, not the appearance (e.g., &#8220;Print&#8221; for a printer icon); for complex images such as graphs, provide a complete text equivalent of the data. If it&#8217;s hard to decide, follow the W3C&#8217;s &#8220;alt decision tree&#8221; and check in order: is it a link or button \u2192 does it add meaning to the page \u2192 is it purely decorative. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/decision-tree\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Common mistakes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>alt<\/code> Leaving out<\/strong> entirely &#8211; without the attribute, some screen readers read the file name as-is, confusing users. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/decorative\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a><\/li>\n\n\n\n<li><strong>Keyword stuffing<\/strong> &#8211; <code>alt=\"puppy dog baby dog pup pups puppies...\"<\/code>: filling the attribute by repeating the same meaning over and over like this, which Google treats as a spam signal. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li>\n\n\n\n<li><strong>Filler prefixes like &#8220;Image:&#8221; or &#8220;Photo:&#8221;<\/strong> &#8211; generally unnecessary. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/li>\n\n\n\n<li><strong>Adding descriptions to decorative images<\/strong> &#8211; it becomes noise when read aloud and gets in the users&#8217; way. <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/decorative\/\" target=\"_blank\" rel=\"noopener\">W3C<\/a><\/li>\n\n\n\n<li><strong><code>alt<\/code> skipped in favor of the <code>title<\/code> attribute<\/strong> &#8211; <code>title<\/code> is usually a tooltip that appears only on mouse hover, so keyboard and touch users can&#8217;t see it. <code>title<\/code> cannot replace <code>alt<\/code>, and if you duplicate the same text in <code>alt<\/code> and <code>title<\/code>, screen readers read it twice and cause confusion. Put important information in <code>alt<\/code> or the body text. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTML\/Reference\/Elements\/img\" target=\"_blank\" rel=\"noopener\">MDN<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">References<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/google-images\" target=\"_blank\" rel=\"noopener\">Google image SEO best practices<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/\" target=\"_blank\" rel=\"noopener\">Images Tutorial (image accessibility guide)<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/informative\/\" target=\"_blank\" rel=\"noopener\">Informative Images<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/decorative\/\" target=\"_blank\" rel=\"noopener\">Decorative Images<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.w3.org\/WAI\/tutorials\/images\/decision-tree\/\" target=\"_blank\" rel=\"noopener\">An alt Decision Tree<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTML\/Reference\/Elements\/img\" target=\"_blank\" rel=\"noopener\">img element (alt vs. title)<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.searchenginejournal.com\/ranking-factors\/alt-text\/\" target=\"_blank\" rel=\"noopener\">Is Alt Text A Ranking Factor? (coverage of John Mueller&#8217;s remarks)<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.semrush.com\/blog\/alt-text\/\" target=\"_blank\" rel=\"noopener\">What Is Alt Text? (length and writing guidelines)<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Alt text is a short piece of text placed in the alt attribute of an img tag to describe an image in words, and is often called an &#8220;alt tag.&#8221; Its original main purpose is accessibility: screen readers read it aloud for users who can&#8217;t see the image. At the same time, Google uses it as a signal to understand what the image shows, so it also affects image search.<\/p>\n","protected":false},"template":"","glossary_categories":[19],"class_list":["post-262","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-onpage"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/262","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/262\/revisions"}],"predecessor-version":[{"id":2347,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/262\/revisions\/2347"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=262"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=262"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}