A card opens through an onClick handler, but its markup has no link address — href. A user can navigate with a regular browser, but link extraction cannot find the URL. The card has its own URL. Make it a regular link so people can copy the address or open the content in a new tab.
Links open pages; buttons perform actions
Google generally crawls links represented by an a element with an href attribute. Official documentation.
An article card has its own URL, while a filter button changes the current interface. These elements may look alike, but they serve different purposes. Start by classifying their behavior rather than globally replacing button with a. For navigation, users expect to open a new tab, copy the address, and go back. For an action, they expect an operation to happen in the current context. A link preserves these familiar browser actions and lets search engines discover the URL. Keep buttons for actions such as expanding a filter or submitting a form.
What to keep as a button
| Interface element | What happens when clicked | How to implement navigation | How to check the link |
|---|---|---|---|
| Article card | Opens the article | Use a link | Has an href |
| Open filter | Local action | Keep it as a button | Accessible controls |
| Submit form | Sends data | Keep it as submit | Correct action |
| Client-side router | App navigation | Check the rendered HTML | A real link |
Check the rendered markup
Check the rendered markup, not the name of the React component. A Link component may output an a element with href, while a custom NavigationButton may be only a div with a handler. Check both the source HTML and the final DOM, since links may appear after rendering. The element must have a valid address, not javascript: or an empty fragment, if it is meant to open a separate page. Then open that address directly. Having an href does not confirm that the destination works, so check the target page's status and content separately.
<a class="card" href="/articles/example/">Читать статью</a>
<button type="button" aria-expanded="false">Открыть фильтр</button>You can keep the card styling as it is. Navigation has its own URL; a filter performs a local action. If you use a router component, it must output an a element with the correct href in the final DOM.
Open the card in a new tab
Try opening the article card in a new tab using the browser's usual action, then navigate to it using the keyboard. Copy the link address and paste it into a new tab without first loading the app into a particular state. The filter button should still expand the panel, keeping focus according to the intended behavior. An additional test without JavaScript can help reveal dependencies, but it does not replace understanding the client-side site's architecture. For a client-side app, check the href, direct URL access, and keyboard controls. A site can use JavaScript while preserving the usual features of links.
Keep the styling without nested buttons
Keep the card styling with CSS, using a link for navigation. If the card contains other actions, check that the structure is valid and there are no conflicts between nested interactive elements. Do not wrap the entire area in a link if that would make the add-to-cart button accidentally open the product instead of performing its action. A router component can speed up navigation if the rendered HTML still contains a regular link. Check focus-visible and the accessible name. Do not add an invisible link next to a clickable button. Make the navigation itself a link, with clear text and visible focus.
Check navigation and the remaining action
The card opens with a regular click, Enter, and in a new tab. The copied address works directly without visiting a previous screen. The filter button still expands the panel and does not send the user to another page.
Read also: How HTML errors affect SEO and indexing and SSR vs CSR vs SSG for SEO: what to choose in 2026. Website checks are available on the reChecker technical audit page.