Inspect before you click: change a link in browser DevTools
A link’s label is not a guarantee of its destination. A “Click here to proceed” button may point to a tracking service, a download, a login page, or a replacement domain. Learning how to use browser DevTools to modify the link URL before clicking shows what the browser is asked to do, without relying on reassuring wording.
Chrome, Edge, Firefox, and Safari all provide developer tools, although their menus differ. On Windows, Ctrl + Shift + I usually opens them; on macOS, Cmd + Option + I does the same. Safari may require enabling the Develop menu first. The relevant panel for this job is Elements, where you can examine the HTML behind a visible link.
Think of a link as three questions: where does it point, what happens when it is activated, and what information does the destination request? The href attribute answers only the first. A link may also carry an onclick handler, open a new tab, or redirect after the request begins. A harmless-looking URL can still collect data or lead somewhere unexpected.
In Australia, this check matters when a link arrives through social media, a marketplace, an SMS, or a QR code at a café in Melbourne or Sydney. People browse on mobile data, tap promotions while commuting, and use shopping accounts on shared devices. Pausing before opening an unfamiliar destination is simple, portable, and part of everyday digital hygiene.
Why the visible link can mislead
Marketing language often compresses a complicated route into a generic instruction. A page may show “Continue” while its anchor contains an affiliate identifier, a shortened address, or unfamiliar parameters. A relative path can make a page look as if it belongs to the current site even though the final host is elsewhere. Inspecting the markup exposes the difference between the words on screen and the address behind them.
Design also shapes behaviour. A hurried tap on a deadline, a flashing promotion, or a button resembling a familiar brand can make a suspicious link feel legitimate. Understanding click psychology can explain why labels influence decisions, and that influence is a reason to inspect the destination rather than proof that it is safe.
Inspect the destination before opening it
Right-click a link and choose Inspect, or open DevTools and use the element picker. The Elements panel highlights the corresponding <a> element. Look for href, then read its full value rather than only the visible text. In many browsers, right-clicking also offers Copy link address, which puts the destination on the clipboard without navigating to it. Hovering may reveal the same target in the status bar.
Check what kind of value you have found. A relative address such as /go depends on the current domain; mailto: opens an email client; tel: starts a phone call; and javascript: may execute code. None is automatically fraudulent, but each deserves a different response. If the element has no href, inspect nearby scripts and event listeners before activating it.
Replace the link URL in Elements
To change it directly, double-click the value beside href in Elements, paste a known address, and press Enter. The edited anchor now points to that location, but the change exists only in the current page and disappears on refresh. Expand the element to check target, rel, and onclick; remove or neutralise an inline handler if it could override the new destination.
For repeated checks, select the anchor in Elements, switch to Console, and use the selected-element shortcut $0. The command $0.setAttribute('href', trustedUrl); $0.setAttribute('target', '_blank'); $0.setAttribute('rel', 'noopener'); $0.removeAttribute('onclick'); changes the destination and opens it separately. Here, trustedUrl represents a full address you have already verified. Avoid running commands supplied by an unfamiliar page.
Test the edited destination safely
After editing, hover over the link to compare the displayed target with your replacement. Hold Ctrl on Windows or Linux, or Cmd on macOS, while clicking to open it in a new tab; the middle mouse button offers a similar option. A private window can reduce the effect of stored cookies. Before entering a password, payment detail, or personal record, verify the hostname, HTTPS connection, and path, not merely a familiar logo.
Some destinations redirect again, so an edited URL may still lead elsewhere. If a page points to a directory, such as a community resource hub, copy the address into a new tab and check each redirect instead of trusting the label. If a sign-in appears unexpectedly, close the tab and return through the organisation’s known website or app.
Follow redirects and dynamic link handlers
Use the Network panel to see the route a request takes. Enable Preserve log, clear the panel, and then open the edited link. The request list shows the first address, intermediate hops, and final document; the Headers or Initiator view can explain which element made the request. Shortened links and affiliate redirects commonly add hops, while some sites replace the visible destination only after JavaScript runs.
Dynamic pages need a different approach. If clicking a text item changes the address without an obvious href, inspect event listeners and search the page for anchor elements. A site’s navigation menu can contain several routes hidden behind one control, so examine the selected element and the resulting request separately. Pause when a button changes the URL without showing where it points.
Account for Australian law and local practice
Inspection supports better security decisions, but it does not replace consumer and privacy law. The Privacy Act 1988 and Australian Privacy Principles govern many organisations that handle personal information. The Spam Act 2003 sets rules for commercial electronic messages, including consent and unsubscribe requirements, while the Australian Consumer Law prohibits misleading representations about prices, benefits, and payment arrangements. These rules matter when a link promises a free trial that quietly creates a subscription.
Australian shoppers often encounter links from small retailers using Shopify or WooCommerce, as well as councils, ticketing agents, and local service providers. Check for an Australian business name, an ABN where appropriate, a genuine contact route, returns information, and a plausible domain before paying. On public Wi-Fi in a Melbourne café or a Sydney transit hub, prefer mobile data or a trusted VPN for sign-ins. Where a legitimate provider supports PayID or BPAY, confirm payee details in its official app rather than through a shortened link.
If a page requests remote-control permission, personal records, or a one-time code, close it and preserve a screenshot. Report suspected scams to Scamwatch and the relevant platform, and contact your bank promptly if money is involved. You are not obliged to complete a flow simply because its design makes it difficult to leave.
Make the next click an informed choice
Use a repeatable sequence: inspect the anchor, read the full destination, remove conflicting handlers, open the result in a new tab, and check the final domain before sharing information. On a phone, long-press the link to copy its address or use the browser’s link preview. On a desktop, DevTools provides more context when the markup sits behind a script.
Open the suspicious page now, right-click the “Click here to proceed” link, inspect it in Elements, and replace the URL with a destination you have independently verified. Read the Network trail, confirm the domain, and only then decide whether to continue. That brief pause can stop a redirect, credential request, or unwanted payment from becoming the next click.