An audit export can list hundreds of warnings. It cannot, by itself, explain which issue matters, whether you verified it or what you personally contributed.<\/p>\n
A useful portfolio entry answers a smaller question: What did you observe, how did you interpret it, and what would establish that the work was complete?<\/strong><\/p>\n This article follows one fictional SEO finding from observation to interview explanation. It is a practice example\u2014not an audit of ASDM, a real client project or a student success story. The page paths and findings are invented. No change has been deployed and no traffic improvement has been measured.<\/p>\n For the broader structure of a beginner portfolio, start with our digital marketing portfolio guide<\/a>. Here, the focus is the reasoning inside one SEO work sample.<\/p>\n For this exercise, imagine a small furniture workshop with a public guide called \u201cChoosing a dining table size\u201d. The owner wants prospective customers to discover the guide through search.<\/p>\n Your permitted task is to review that guide and prepare recommendations. You do not have permission to change the website.<\/p>\n Write the boundary before listing issues:<\/p>\n In a real assignment, confirm these points with the owner. A page deliberately excluded from search is not automatically a mistake.<\/p>\n Suppose the exercise supplies this HTML fragment:<\/p>\n A careful observation is:<\/p>\n The supplied example contains a noindex instruction, while the exercise brief says the guide should be discoverable in search.<\/p><\/blockquote>\n An unsupported conclusion would be:<\/p>\n This tag caused the business to lose customers.<\/p><\/blockquote>\n You have no customer records, search history or causal evidence for that conclusion. You have identified a potential mismatch between an instruction and the owner’s stated intention.<\/p>\n Google’s noindex documentation<\/a> explains that it can process this rule in a robots meta tag or response header when it can access and crawl the page. Blocking that access with robots.txt can prevent Google from seeing the rule.<\/p>\n That distinction matters: recording a tag in a supplied fragment is not the same as verifying what Google last fetched.<\/p>\n Use the example to practise a short record:<\/p>\n<\/span>1. State the review boundary<\/span><\/h2>\n
<\/span>2. Describe the observation without jumping to a result<\/span><\/h2>\n
<!-- Illustrative input, not captured from a live website -->\n<meta name="robots" content="noindex"><\/code><\/pre>\n<\/span>3. Build a finding card someone else can check<\/span><\/h2>\n